Fernando, what's the latest on the x58 Intel AHCI users? Have you had any updated opinion on the driver/OROM they should use for best performance? What about x58 AHCI + Samsung 840 Pro 256GB with RAPID enabled -- any update on best driver/OROM to use?

@ Fernando :

I have run the 12.9 driver from the day it was on Station Driver, and my DEV ID is 2822. I don't know if you saw what I said about the Intel RST being 2822, and one poster said it would show as 55aa because the SataDriver 11 in our BIOS was using the 2822, which I don't get because I figured the Dev ID is a hardware ID, and just because the BIOS has two SataDrivers in it they still should be 2822.

As for my MOD, Hanson modded my BIOS, I don't know what he used for me, maybe he will see this and post it. I tried the one on Station, then tried one posted by lordkag, I couldn't get them to work so when Hanson modded my BIOS for me I used it, I never tried the one you have.
I always use the regular one you post, I never use the one modded for the X79 you post, because Asrock made my BIOS support the RST. They have always worked in the past.

I don't get the HEX of the SataDriver, I not exactly sure of which exact offset, or offsets needs to be the same for me to use a RST EFI SataDriver. I hope someday you could post an exact guide to changing a SataDriver so we could change the info to match the one already inserted in out BIOS, but the newer version.

Hello everyone
Thanks for your answer to my question.The MMtool is not work for me ,because I tried it early,that is true my BIOS is from Award BIOS.
I am a Chinese man,my English is not enough for do this work.Ago I tried to do this work (mod BIOS) by some tools like cbrom with Chinese language translation,but the modding BIOS didn't work. I think the real reason is MINIT module was wrong and Translation tool with some bugs.
So I beg you mod the bios file F9d ,I wil try flash it.
My E-mail is jyp007@21cn.com.Plese mail me.

@odiebugs

Your RST device has a hardware ID of 2822, but it can't have the same ID for multiple OROMs. What you see as 55AA in MMTools is just an anchor or a signature to know what module it is. If they would have the same 2822 ID, how the BIOS would know what OROM (11.x or 12.x) to use when a 2822 device gets loaded? This way, depending on how the BIOS is coded, it loads 2822 with 11.x drivers and it seeks for 2822 anchor, or it loads 2822 with 12.x drivers and it seeks the 55AA anchor. You can change the drivers to any version you like, but the BIOS will pair RSTe 2826 with a 2826 anchor and RST 2822 with a 55AA or a 2822 anchor, depending on BIOS settings. If you want to test, I can provide the SataDriver11 module updated to 12.9, but I think it will not get loaded. You can also replace in MMTool the 8086-2822 link with 12.9 OROM, but again, my guess it will not get loaded - instead, 55AA seems to be preffered for RST 2822, since it is a newer version.

For UEFI drivers it is simpler, because each module has its own GUID, so it would load Satadriver for RSTe and SataDriver12 for RST. Do you have any option in BIOS to switch between SataDriver11 and SataDriver12?

Again, do not mix IDs with GUID! You only care about IDs when you are in Legacy = CSM enabled. This way the OROM gets loaded and you have seen that the anchor 55AA has higher merit for RST, while the anchor 2826 is reserved for RSTe. In pure UEFI = CSM disabled it will load GUID 5BB2F356-114A-4105-A5B2-9A9741DCD365 (which is now SataDriver12) for RST and GUID 43A0A7B3-1E92-42EF-A46D-DDC03E52CB5C (which is now SataDriver) for RSTe.

Final thought: just because Intel released a new driver, don't expect it to be flawless. See what other users have to say, ask Hanson for a feedback, since he has a similar board. You can replace your SataDriver12 with one of the files uploaded here, but I don't know if your board will work with a different GUID than the original 5BB2F356-