As I already have written: The UBU tool has never added and will never add any natively not present BIOS module. It is an “UEFI BIOS UPDATER” (=UBU) and not an “UEFI BIOS INSERTER” (=UBI).
You wouldn’t have gotten the error message, if you would have used the ASUS USB Flashback method the correct way.
The UBU tool is able to detect the NVMe module, if it is already present within the BIOS, but it cannot insert a missing NVMe module (see above). By the way: Although all BIOSes, which natively do support NVMe, contain the mentioned 3 different NVMe modules, users of an older Intel chipset system just have to insert 1 single module and will get full NVMe support. >Here< is the related guide, which contains download links to the universally usable NVMe module.
I’m sure this has been asked before, and I am sorry if it has but my search for “DX58” returned nothing in this thread.
I’m trying to use UBU to update the IRST RAID OROM in my Intel DX58SO UEFI bios v5600 to use the TRIM-supported patched v11.2.0.1527. I’ve located a copy of MMTool 5.0.0.7 but when I run UBU.bat I get a message that the ROM is an “Unknown Version AMI Aptio”.
I’ve tried opening the ROM file directly in MMTool 5.0.0.7 and get the error “Firmware Volume open error”. When I open it in MMTool 4.50.0023 it opens but I only see two “volume indexes” (is that the right term?). Neither have a filename. One has GUID 7A534591-37CE-4881-B3C9-713814F45D6B and the other F5CF71AB-B04B-4B7E-988A-D8A0D498E692.
When I open it with UEFITool v0.22.1 I see the same two indexes in the Structure window and the Messages window says “parseSection: GUID defined section with unknown authentication method” and a few lines of “parseFile: invalid data checksum 5Ah, should be 00h” with some more after that.
Can anyone help me mod this BIOS or perhaps already have a DX58SO v5600 BIOS with a patched IRST 11.2.0.1527 OROM already inserted?
Yes, thank you. CodeRush has graciously been communicating this to me via PM. I understand I may have to use a SPI programmer to read the contents of the chip into a readable binary format.
I’ll need to determine if the SPI chip is socketed or soldered on the DX58SO. I’m not going to bother if I have to desolder. My best option might be someone else with an Intel DX58SO who has already completed the steps to dump the SPI to a binary file.
No need. In the future I’ll open a Microcode repository thread (like the Engine one) for Intel, AMD, VIA and Freescale (what MCE currently supports). In the meantime, I don’t (personally) plan to upload/attach here all updates shown at newer MCE DB releases so people shouldn’t ask. I’m ok with a few microcodes which are found at UBU but the rest will have to wait until the repository thread is up.
Guys, I don’t understand why DB r49 became so popular all of a sudden but as I’ve explained here, you need to wait until the repository is released, early next year.
good to see You! Yes You miss for everyone! Wecome on the board !!!
