@ lordkag :

Thanks. I just figured because you highlight the Satadriver in only replaces the one in that area, but what you said makes sense. I am not sure why we have SataDriver 11, we never use it and we can't run it, only SataDriver 12, or CSMCORE is used, Bios or UEFI.

Yes, I begged Asrock, sent them so many emails they finally added ROM switch to BIOS last year. I have only used the DEV ID in MM tool for CSMCORE, and I just update the SataDriver 12. Every time I update a ROM/Driver, driver I run winsat diskformal, do a CMOS clear, then run AS-SSD, not in that order. I always try each RST driver, but look for the last of each series because they have the most Resolved Issues for that series.


I tried to get Asrock to make the rom switch to be able to give three options under the RAID option- RST 11, RST 12. RSTE. They wouldn't. I wanted to test the last 11 series, TRIM, Speed on any OS we use.

Zitat von Fernando im Beitrag #268

---

Why do you want to modify the modules yourself? The risk to do something wrong is very high and I am offering already modded Intel RAID ROM/SataDriver modules.
If you want to try a modded SataDriver module v12.9.0.2006, please let me know what you want to get modified and I will send you a PM with the link. Then you will be able to compare the modded hex code with the original file.

Request: Please add a signature to your posts. This will make it much easier to help you.

---

@ Anyone.

Sorry if I didn't read enough. Will the 13 series RST be able to work on the X79, with people who have the option of a RST in BIOS. I tried to insert it but failed, but I also failed with the 12.9, so I was wondering if it was me, but I noticed Fernando doesn't have a 13 modded for X79 for those who use the RSTE.

@odiebugs

Maybe this image will help you understanding the difference between real ID and the linked ID. As you can see, a single OROM module can be linked to many IDs, without duplicating the module or the ID. What you see in MMTool is just a link or a shortcut to a module, which is highlighted in green. The real ID (the one embedded in hardware) is to be found somewhere in that OROM, next to the string PCIR. So when you replace a link with MMTool, you keep the link and only replace the module with one that has a similar ID next to PCIR.

For you and @hanson
I have modded your RAID drivers with all the latest version for each series. They have a name in the form of the ffs to replace and the version contained, i.e. "SataDriver12 - 11.6.ffs" will be used to replace SataDriver12 with a module containing Intel RST 11.6.x. It will still keep the name SataDriver12 after replacement, to not confuse or scare you, but if you want to also change the name to something like SataDriver116 and so on, it could be done. You will also find two "SataDriver - 3.x.ffs" modules which can be used to update the SataDriver (this is the UEFI driver for RSTe) to 3.7 or 3.8.

For the OROM you can do it yourself, by replacing 8086-2826 or 8086-55AA with the version you like.

@lordkag

Hey thanks a lot, I really appreciate that. By the way do you have any idea regarding the ASMedia 0.954 matter (no booting possible)?

Best wishes hanson

I think you should test with all these versions - 0.93.1, 0.95, 0.951 and 0.954. If you get a problem with only some of them, then it is Asmedia's fault. If you get a problem with all of them, you can try your luck with Asrock support and ask them to provide a patch. As much as I would like to help, this module is a single piece and I wouldn't know where to look for patching.

@ lordkag :

Thank you for the files. I have always just used replace in MM tool. I replaced the 12.7 series with the 13 you posted, checked with hex and it was 13, but when I flash the BIOS, it's still 12. Should I use the " for option rom only " I never had to before, and only with CSMCORE.
This is the same thing that happened with 12.9, never had a problem until trying 12.9. Thanks for any help.


***** I took Fernando's 13.1 and used the option rom only, under replace and used the 55aa and it worked.

@Fernando

So, for a Rampage Formula ( X48/ICH9R), i just replace the default 8086_2822 ROM with this one :

>"Universally TRIM modified" Intel RST RAID ROM v11.2.0.1527 with TRIM in RAID0 support<

without modifications ?

Using the "replace" function of MMtool, or "extract"->"insert" ?

Zitat von Fernando im Beitrag #281

---

Zitat von felix im Beitrag #280

---

So, for a Rampage Formula ( X48/ICH9R), i just replace the default 8086_2822 ROM with this one :
>"Universally TRIM modified" Intel RST RAID ROM v11.2.0.1527 with TRIM in RAID0 support<
without modifications ?

---

Yes!

Zitat

---

Using the "replace" function of MMtool, or "extract"->"insert" ?

---

You can either simply use the "Replace" tab (easiest way) or - one after the other - the "Delete" and "Insert" tab.
Using the "Extract" option will not change anything within the BIOS.

---

Thank you for your fasst reply!!!

Yes, i wanted to write delete, extract is just to copy in a binary file the rom.

Current Rom in latest bios ( 1001 ) is v7.5.0.1017 and i am using Samsung 840 Pro with "Universal 64bit Intel RST AHCI & RAID driver v11.2.0.1006 mod by Fernando" driver in Win7 x64.

Do you think that using 11.2.0.1527 rom will be great improvement in SSD performance ? Will i have to revert to msahci before flashing and re-install modded driver after flashing, or driver will not be a problem ?

Thank you in advance for your help.

Thank you for your help, Fernando.

SSD is in AHCI, but if i find 2 spare drives i will also check TRIM capability in RAID for ICH9R.

@ Fernando :
Thanks again for the help, has something changed from your guide on win lite. Legacy ( BIOS ) was to do a CSMCORE, with a 2822. UEFI SataDriver was just replace SataDriver. I am running in UEFI, my SataDriver is a RSTE, my SataDriver 12 is a 12.7 OROM.
But like lordkag said, my SataDriver 11 shows 2822 and 12.7 shows a 55aa. I tired to replace the SataDriver 12, didn't work, but it did show it worked when checking with hex. I then went to replace again, I checked the option rom only and picked 55aa, and it worked.

I thought we only checked OPTION ROM for legacy ( BIOS ) and just replace for UEFI for SataDriver. I am lost, but what I did worked.

@odiebugs

Even though everyone is telling you otherwise, you keep confusing [Legacy -> CSMCORE -> 8086-55AA] with [UEFI -> GUID -> SataDriver12]. I can understand that you don't trust what I write, but at least you should respect Fernando and his work and read the guides he posted in this forum. It has helped a lot of us.

Please forgive me, but I have nothing else to comment on this matter. I will add the steps to do it yourself; if this doesn't helps...

Legacy OROM:


UEFI Driver:


I will add one more thing:
- for Legacy -> OROM you should update with the same inner ID, the one inside the module. The link ID is just for BIOS use, to deal with all the modules. Your case: the OROM 12.7.x has 8086-2822 inner ID, but the link is 8086-55AA.
- for UEFI -> Driver you should update only with a file that has the same GUID. There is also the case of DXE Dependencies, but this is another story.