@Lost_N_BIOS

I have checked on Marvell RAID Utility, it does not detect the device.
I have installed this mrvl_utl_msu_4.1.10.2046_windows_x86-64 found on station-drivers.com
I tried MarvellCLI Utility and it shows No Adapter Found.
Which Marvell Driver app are you referring to? I cannot find it.
I cannot check the detailed version numbers.

It may only be for Marvell 9128 boards, sorry for any confusion, what I meant is usually posted on the motherboard driver/utility download pages. Sometimes that may only look like a "driver" package, I'll check your boards download page.
I don't see it, but I do remember the name now Marvell Storage Utility, it's like Intel's RST software, shows you info and can build RAID on 9128 I know because I've used it there, but unsure if it's for or compatible with 9123
Yes, here from your boards page, it has a console in one of the folders - https://dlcdnets.asus.com/pub/ASUS/misc/...XpVistaWin7.zip

Did you try the DOS package again, using the three commands I showed? Or were you wanting to check before/after as I mentioned?
I guess that may not be possible if there is not a utility for 9123, and there may not be since the one I was thinking of was for RAID/9128, not sure if 9123 can even do RAID

I think I have a P7P55D-E (No PRO) here I can setup and figure this all out on my end if you want, at least that way I can figure out the BIOS before I send it to you

I know with the DOS FW update tool you were using and MVF_Mag inside there, you can dump the current FW to file, and maybe w/ -v (verbose) it will show you info
But I'll have to figure out how to dump the chips FW on my end because the stock BIOS only has complete orom (not the other two parts Bootloader/FW, they are partial in the stock BIOS)
Go.bat can be used in that way too, but I don't think it will fully show what we want to check (I think it's for checking info on the input file
go -v Show verbose message
go -r Read back binary file, no flashing

* Edit - ahh yes, this post shows what I was thinking, user read back info from the onboard chip using Go.bat -v -r
[Discussion] Marvell 91xx/92xx SATA3 Controller BIOS modules

I'll figure this out on my end, give me some time (Sorry for the delay, but I'd rather get it right than hand you another improperly functioning BIOS)

@Lost_N_BIOS - I have not run the update with the three commands yet, I wanted to see the version info first.

I ran GO.BAT -v -r and it displayed the following info:
Adaptor Info
DevId: 9123 DevFunc: 00 Bus: 09
ClassCode: 0106 RevId: 10 Ver: 00
FlashCount: 01 SubVer: 00

Incoming Image Version is 1.0.0.1808
Incoming Autoload Version is 200060c - CPU_AHCI_9123_NDO
Current Image Version is 0.16.0.4116
Current Autoload Version is 1001802 - PT_AHCI_9123_NO_MATH

I am going to run the DOS update with the 3 commands, will post back later once done.

@Lost_N_BIOS - I've run the DOS FW update with the 3 options and it shows update successful but when it boots up it still shows OROM 1.0.0.1025.

When I ran go GO.BAT -v -r its displays the same info as before;
Adaptor Info
DevId: 9123 DevFunc: 00 Bus: 09
ClassCode: 0106 RevId: 10 Ver: 00
FlashCount: 01 SubVer: 00
Incoming Image Version is 1.0.0.1808
Incoming Autoload Version is 200060c - CPU_AHCI_9123_NDO
Current Image Version is 0.16.0.4116
Current Autoload Version is 1001802 - PT_AHCI_9123_NO_MATH

It doesn't seem to work.

Thanks, seems that is only checking the autoload and FW image, not the rom itself. I guess this probably is one of the boards mentioned in the main thread that can only be updated via BIOS mod, I'll have to see what I can figure out on my end.
Or, if you don't want to wait, I can go ahead and do the marvell mod by itself, first using 10.8 RST and secondary with 11.2 and you can test if Intel and Marvell work on each or not.

I initially suspected either the Marvell mod is not done correctly (due to his comments and non-Marvell BIOS included as if he already knew or hadn't tested and didn't trust), or Intel RST version caused the issues.
But, after reading more about the Marvell mod, seems maybe the Intel RST isn't such an issue once Marvell is done correctly (and this BIOS all messed up anyway, stock is set for 9120 and so he did mod to 9120 too, surprised both don't fail)

What I don't like, and what caused me to pause and dig deep into all this, aside from the stock BIOS having 9120 as an ID in these files, is the stock BIOS E7 module (FW Image) is 3kb, while replacement/update is 200kb
However, this may be due to BIOS only holds small portion and rest was already programmed in chip by Asus, or is larger in BIOS when they update within BIOS at certain BIOS versions.

@Lost_N_BIOS

If it is safe to test the mod BIOS (marvell mod by itself, first using 10.8 RST and secondary with 11.2), then it's fine, I can do that.
If it doesn't work will I be able to flash back to stock or previously modified one?

@rylan74 - Yes, it would be fine for you to test these BIOS, if failed then the Marvell ports simply wouldn't work right just like you have now. And yes, you would be able to then flash back to stock or whatever BIOS you are using now.

Here, this contains several BIOS.
1. Same BIOS mod you gave me originally, but with 10.1.0.1008 RST instead - so still 9120 ID'd Marvell Roms
2. Same BIOS mod you gave me originally, but with Marvell ID's changed to 9123 instead (@ E6+ID20) - so still RST 11.2.0.1527
3. New BIOS I made, RST 10.1.0.1008+ Marvell updates @ 9120 - similar to BIOS-1 edit above, but made fresh, missing other edits from previous mod
4. New BIOS I made, RST 10.1.0.1008+ Marvell updates @ 9123
5. New BIOS I made, RST 11.2.0.1527+ Marvell updates @ 9120 - similar to previous mod, but made fresh and missing other rom updates
6. New BIOS I made, RST 11.2.0.1527 + Marvell updates @ 9123 - very similar to previous mod, but with correct Marvell ID's - missing other rom updates for now.
http://s000.tinyupload.com/index.php?fil...643146413758870

Once we find working solution for these two, I will update the rest. If none of these work, as in show updated Marvell version and RST also works, then I'll have to setup a board on my end and figure this out.

I found @lordkag posted that MRU utility I was thinking of, and explained it's usage here for getting device info, you can see if it works with 9123 or not (I'm not sure)
[Discussion] Marvell 91xx/92xx SATA3 Controller BIOS modules (6)

@Lost_N_BIOS

I will test these out and let you know.
Thank you,

@Lost_N_BIOS

I have tested these BIOS and had issues with them.
BIOS 2, 4 and 6 seemed okay, but after a few minutes in Windows the hard drive/s connected to Marvell ports would disappear.
Windows Event Viewer Logs were showing various errors about atapi error, resetting the device, and device not responding. I tried with IDE, AHCI, Marvell drivers and standard MS drivers.
I could use CTRL+M to get into Marvell RAID BIOS. MRU also showed the device and drives connected.
As soon tried to copy data or use CrystalDisk Mark to test, the PC would freeze every few seconds and disks would disappear.
I tried flashing the other BIOS, but somewhere along the way the Marvell Device ID changed to 914D, it was showing 914D in BIOS RAID menu and MRU Utility, but still the same problem with disks disappearing and PC freezing.
I tried the other BIOS as well and same issues and at one point I thought the Marvell Controller died as it was not detecting drives anymore.

Tried to flash back to stock ASUS BIOS but also had some issues with the Marvell Dev ID, only way to fix it was to remove drivers, clear CMOS, flash stock BIOS again, now it is working again using MS AHCI driver, Windows shows Dev ID 9123. It does also work with the Marvell driver but I'm not sure if it is better to stay with MS driver or use the Marvell driver?

In the Marvell RAID BIOS and MRU it showed supported modes as RAID 0 and RAID 1, I did not have another blank disk to test RAID config, as it is also not my intention to use RAID on the chip. It should have been able to do AHCI/ IDE "passthrough" to use standalone disks, perhaps this is an issue with the way "passthrough" works.

@rylan74 - When you see this on Marvell, is the drive connected a SSD, or regular HDD? Marvell often craps out like that with SSD from all that I've ever experienced with it on many boards, but if this only happens to you with these BIOS and not the original stock BIOS (With same/similar testing done on same disk) then it's the roms causing the issue.

So BIOS 1, 3, 5 all have this Marvell ID error? Please clarify so I can check, you said "other BIOS", and "other BIOS" so not sure what all that applies to.
Those were all set to your original BIOS ID of 9120, but once you confirm I will rip them apart and check to be sure I didn't edit anything in incorrectly (went ahead and looked at the files I inserted for all, and each one set to your original device ID 9120 (20 91 in hex)

You should use AHCI or RAID w/ single disk, IDE should not be used, shouldn't even be an option these days

Sounds like this update is either not compatible or ideal for your system, unless you were using SSD for the testing you describe above, if that's the case then it sounds like normal/common Marvell operation with SSD to me (ie test again with HDD and I bet it's fine)
All Intel ports working fine still too in all?

@Lost_N_BIOS

I tested each BIOS again, with flashing back to original ASUS BIOS in-between each mod BIOS test. Tested with 1x HDD, then 1x SSD and then 2 HDDs connected to Marvell Ports.
When I refer to boot into Windows, the OS is on Intel port with SSD, not the same SSD that was used to test the Marvell ports.

BIOS 1: Marvell does not work. Does not boot into Windows.
BIOS 2: Updates Marvell, can CTRL+M. Does boot into Windows. IDE Mode shows Dev ID 914D, AHCI Mode shows 9123. Disks disappear from Windows. Errors in event viewer - Disk IO, device reset, Disk removed, etc.
BIOS 3: Marvell does not work. Does not boot into Windows.
BIOS 4: Updates Marvell, can CTRL+M. Does boot into Windows. IDE Mode shows Dev ID 914D, AHCI Mode shows 9123. Disks disappear from Windows. Errors in event viewer - Disk IO, device reset, Disk removed, etc.
BIOS 5: Marvell does not work. Does not boot into Windows.
BIOS 6: Updates Marvell, can CTRL+M. Does boot into Windows. IDE Mode shows Dev ID 914D, AHCI Mode shows 9123. Disks disappear from Windows. Errors in event viewer - Disk IO, device reset, Disk removed, etc.

Tried to create a RAID 0 with 1x HDD and 1x SSD. It creates the RAID_VD, boots into Windows then Disks disappear. Errors in event viewer - Disk IO, device reset, Disk removed, etc.

Back to stock ASUS BIOS and everything works again. No issues with SSD and HDD on Marvell ports.

1. Same BIOS mod you gave me originally, but with 10.1.0.1008 RST instead - so still 9120 ID'd Marvell Roms
3. New BIOS I made, RST 10.1.0.1008+ Marvell updates @ 9120 - similar to BIOS-1 edit above, but made fresh, missing other edits from previous mod
5. New BIOS I made, RST 11.2.0.1527+ Marvell updates @ 9120 - similar to previous mod, but made fresh and missing other rom updates

So, BIOS above ^^^ seems any update and use of the default Stock Marvell BIOS ID (9120) causes failure
BIOS 2, 4, 6, >> IDE mode and 914D may be normal, expected ID, unsure? IDE mode shouldn't be used by anyone, and this ID is not changed in those tests between IDE/AHCI/RAID (FW always = same ID as I set per whatever # BIOS = ie these BIOS 2, 4, 6, = 9123)

When you tested single HDD, or dual non-RAID HDD, is disk lost fairly quick, is this always, or only under loads and if only under heavy loads is that moving a file or benchmark/testing like CDM?
Marvell is pretty poor performer, like J.Micron, but I've not seen it get killed all that easily with HDD usage.

Sounds like this FW, no matter how it's set, or in what combo with RST, is not working well for this controller.
That or I need to use some combo of new/old, leaving in some module (like possibly the 3KB vs 200KB update at ID 20 FW orom, that seemed wrong right away when I started this, but as mentioned may be due to FW not usually stored in BIOS)

Maybe @lordkag has a few minutes to spare to offer his advice, or check out the BIOS I made at post #22 and see if he thinks I should switch any of that back around with partial stock files

@Lost_N_BIOS

The disk loss is not fairly quick, I can copy a few small size files, but if I try bigger files then it starts freezing and disks disappear. With CDM I use 1GB test.
From what I have read on the forum I see that these Marvell and J.Micron chips are really bad, and I am starting to feel that updating the BIOS modules is a not going to be beneficial .
I have been looking at getting a PCIe SATA expansion card, just not sure on which model to get...
If you can't figure out the BIOS update, then don't worry about it, it's not a major problem, thank you very much for helping me with this.

@rylan74 -Yes, Marvell is worst with SSD especially, it was used on this chipset and few others right before Intel came out with proper 6Gb/s ports. And this one isn't even 6Gb/s anyway it's 5Gb/s actual, any heavy load with SSD and those speeds kill it, slow down, stall out, drop from device manager etc.
This usually doesn't happen with normal HDD due to much slower speeds, but I've not tested it at length with heavy load, it may happen then too but shouldn't be nearly as often or as easy with HDD as it is with SSD

j.Micron, I've never tested with SSD, but in general it's always been meant for an additional storage thing, or CD/DVD etc, not really ever meant to offer a highly beneficial heavy load or high speed solution.

BIOS 2, 4, 6 would be the ideal ones to use, but if they are worse for you than stock, no point in updating to any of those BIOS.
If you need one of those, or some other BIOS, updated with the rest of the roms aside from Marvell let me know what you want edited to what version, and keep in mind that stuff I linked about J.Micron too.

@Lost_N_Bios

I think I'm just going to stick with the stock BIOS.
I'm not using RAID on the INTEL controller, so I guess there will be no benefit to update the INTEL firmware; correct me if I'm wrong?
I'm not using the JMicron controller anymore, and once I get an expansion card, I will not use the Marvell controller also.
I have been advised to look for a SAS RAID card flashed to IT Mode, that will be more reliable.
Thank you.