Zitat von plutomaniac im Beitrag #195

---

Zitat von kevindd992002 im Beitrag #194

---

I'm following the guide to the t, the difference between the two is just not written in the OP.

---

Check what the module that you are going to replace is, compressed or not. Do the same. It only has to do with space constrains.

---

@Fernando

I just replaced the EFI Raid Driver in the BIOS to 12.9.0.2006 and that version doesn't show the RAID menu in the BIOS also. So far the TRIM modified 12.5.0.1815 is the one that showed the menu.

But if you use the "insert as compressed" option in MMTool, does it matter which file is used? Will it further compressed the already-compressed ffs if you use that?

1.) I only updated the previously modded one with UBU. I'm thinking that shouldn't matter, right?
2.) Yes, I powered off the machine BEFORE and AFTER flashing, making sure to drain power (by holding the power button until the red power LED in the motherboard turns off). This was always how I do it.
3.) I haven't tried clearing CMOS yet but when I revert to using the v.12.5.0.1815 then the menu comes back. This confirms that it is really the version that is the problem.

What if I inserted an uncompressed file and then I updated it using UBU? Will it in turn be compressed?

Oh sorry, I forgot. I of coursed pulled out the power cable from the back of the computer before doing all that. So I did really power off the computer. That rules out improper flashing.

Zitat von Fernando im Beitrag #203

---

All BIOS modules, which are inserted into an UEFI BIOS, will be compressed by the AMI Aptio MMTool. So the result after inserting an uncompressed or compressed module, will probably be the same.

---

Zitat von plutomaniac im Beitrag #204

---

According to Intel documentation (and if I understood properly) this UEFI RST Menu location (which is only relevant for RAID arrays) is OEM dependent. That means each OEM must determine where to make it appear. Maybe those efi drivers you are testing are OEM modified (were taken by different OEMs) and it's displayed at some other menu which could be from other UEFI-style menus and that's why you cannot see it.



Also stick to v12.x releases as v13 is not supported by the legacy 6-series systems. And don't worry about compression constantly, it's not important at all. Insert uncompressed, if MMTool complains there is no space -> insert compressed. It's that simple.

---

I totally understand that. I guess I was just confused when you said "All BIOS modules, which are inserted into an UEFI BIOS, will be compressed by the AMI Aptio MMTool."

So if I understand correctly, the insertion of the uncompressed ffs file is still exactly the same process as you would insert a compressed version of it and that is to use MMTool with the "insert as compressed" option. But the uncompressed file only has more information on it like the header.

And all ffs files inside the UBU package are compressed ffs, correct?

While kevindd992002 tends to ask so many questions, some beyond the reasonable limit, I must admit that he is now on the edge of useless/informative.

"Insert as is" means just that, take the file and insert, don't care if it is compressed or not, just need to be well formed ffs. "Insert compressed" means (again) just that, compress the file before inserting. While trying to insert an already compressed file, MMTool seems to be doing nothing, so there is nothing to worry. Besides, this is already done in AMD files, where MISC.BIN is already compressed from AMD, then it is again compressed in ffs. Nothing to be gain, just an increase in risk of errors due to bad decompression.

The compressed ffs must have the same header, this is a requirement and a logical step. Only its sections (but not all) will be compressed. We need to be sure the decompression is 100% accurate, so there can't be enough checks.