@Sonix
Control Panel --> System --> Storage controllers
Asmedia 106x SATA Controller
Asmedia 106x SATA Controller
Asmedia 106x SATA Controller
Intel(R) C600 series chipset SATA AHCI Controller

So how can it be? Their identifier files must be in bios?

And what about invisible:
OROM IRSTe RAID for SATA - 3.5.0.1005 which is visible at Rampage IV Extreme but not visible at Rampage IV Black?

Zitat von Fernando im Beitrag #3825

---

@SkOrPn:
Due to the fact, that lordkag hasn't been online here since August 2016, I doubt, that you will get a reply from him.

---

@Fernando
I may insert AsMedia updated drivers by using mmtool after updating them on Rampage IV Extreme edition, but I have no idea for OROM IRSTe RAID for SATA - 3.5.0.1005 I searched but not found by looking with mmtool.

That line is present at Rampage IV Extreme Edition as well as Asus X79-Deluxe same hardware. Must be at Rampage IV Black Edition too.

@Fernando,

I private messaged him and gave him a link to the proper NEC thread where I documented my troubles with 720201. If he replies I would rather not talk about Renesas firmware here and instead will take the conversation to the proper Renesas thread. Thanks again for these wonderful forums bud.

Rod

@Fernando

Hmm, hex editor trick. OK, thank you very much for response....

I'm trying to update my BIOS on my ASRock Fatal1ty X99M Killer/3.1 using the latest microcodes but every time it keeps stalling at Post Code 94 (CPU error). In fact, if I change something minor like the LAN PXE it does the same thing. I tried MMTool v5.0.0.7, v5.02.0024, and the modified one. Luckily my board has dual BIOS so I'm not SOL but still not sure why it keeps doing that.

Unfortunately, any version of MMTool V completely erases _FIT_ in BIOS for motherboards AsRock X99.

Some feedback regarding Intel CPU microcodes LGA 1155 206A7 - 2D & 306A9 - 1F updated by UBU in Gigabyte AMI Aptio 4 BIOS:

(A) using UBU v1.69.16
(B) using UBU v1.70 a16 Dev

I've checked the modded BIOSes with MMTool 4.50.0.23 & 5.0.0.7.

(A) In MMTool 4.50.0.23 both microcodes show up, as well as in 5.0.0.7.
(B) In MMTool 4.50.0.23 Ivy Bridge CPUID 306A9 (microcode 1F) only shows up (while in MMTool 5.0.0.7 both microcodes show up again).

If we consider compliance with MMTool 4.50.0.23 as a "quality gate" for AMI Aptio 4 BIOSes then there might be an issue with UBU v1.70 a16 Dev.

I've flashed (A) and everything is fine.

@jbmd

I used the patched version of MMTool 5.02.0024 to successfully update my Aptio IV BIOS with LGA 1155 mcodes. With UBU 1.70 a16 Dev it included both SandyBridge / IvyBridge mcodes, as well as correcting for the necessary padding needed between the mcodes (this varies between motherboards).

You can find it for download via a Google search; FYI, the SHA-1 of my copy is 8E54AC68DE355E1031527B89C0560AE1C9C8C508

Thanks, I've used MMTool 5.0.0.7 with both UBU v1.69.16 and UBU v1.70 a16 Dev. I wasn't aware the latter should be used with the patched version of MMTool 5.02.0024 only, thought it was just recommended.
But did you check your modded BIOS with MMTool 4.50.0.23? That was my actual point. UBU v1.69.16 (together with MMTool 5.0.0.7) works for me.
So I just wanted to provide feedback that there might be an issue with UBU v1.70 a16 Dev - but maybe just if you use the wrong MMTool version.

I did not try my modded BIOS with MMTool 4.50.0.23 as the current guidance from the main UBU thread is as follows: "The UBU tool versions from v1.69.12 up are generally usable with the AMI Aptio MMTool v5.0.0.7 and v5.2.0.24, but the best choice will be the usage of an especially patched v5.2.0.24".

The patch for 5.02.0024 is to make it compatible with Aptio IV BIOSes. I'm not sure what the advantage of using MMTool 4.50.0.23 would be at this point, unless you ran into specific problems with the newest version and your motherboard/BIOS.

I didn't mean to use the UBU tool together with MMTool 4.50.0.23. I just checked the result (= modded BIOS) by loading the image in MMTool 4.50.0.23.
Only one microcode shows up in the "CPU Patch" tab (mod performed with UBU v1.70 a16 Dev / MMTool 5.0.0.7). If I check the same mod in MMTool 5.0.0.7 two microcodes will show up.
In my opinion something is wrong here even if the BIOS might work because I consider compliance with MMTool 4.50.0.23 as a "quality gate" for AMI Aptio 4 BIOSes.
Everything fine if I perform the mod with UBU v1.69.16 / MMTool 5.0.0.7 and check it in MMTool 4.50.0.23.

I just used MMTool 4.50.0.23 to check the BIOS image I created with UBU 1.70.a16 Dev and the patched MMTool 5.02.0024. Everything looks good to me (see image below). Try recreating your image using the patched MMTool 5.02.0024; other than that it may be a quirk with your particular MB/BIOS.