MSI BIOS Unresponsive while Using Modified Image

Question

MSI BIOS Unresponsive while Using Modified Image

rackd opened this issue a year ago · comments

Mark commented a year ago

Provide the official URL to the UEFI you tried to modify.

https://www.msi.com/Motherboard/MPG-Z390-GAMING-PLUS/support version 7B51v1E

Did you modify a previously modified UEFI or the stock one?

Stock

What flashing method did you use?

MSI M-FLASH

Did you successfully flash a stock UEFI with said method?

Yes

SHA256 hash of unmodified Setup SCT

3e0d2286b6da0059dfdaf0f124ba57ca3075547a82076f8324f3092637a6b19b

SHA256 hash of IFR Extractor output TXT

9c97e18e492c6839ac9f212628c6efe6816449cc1804d585a80dc17ee06b6677

SHA256 hash of unmodified AMITSE SCT

80115bfd31c9380f777d4134dbe9f1c9e485ae76d2a0d461cd121e426fbe94ec

SHA256 hash of unmodified Setupdata BIN

871d05317b6c77a2479977485ab5cd6eebf7113292cc340eb263ae1d263d5aea

Attach the data.json file with the modification you attempted to do.

I've attached both the stock and modified json files. I've also attached the simple changelog.

data.json.txt
data_modified.json.txt
changelog.txt

SHA256 hash of modified UEFI

f419cd1b251ee9ded6dc6522a70bb19ce147c0c75e700c161f68d485b1e8da8f

Describe the expected outcome as detailed as possible.

I would like to dive deep into this BIOS firmware. My goal of using this very useful tool is to enable certain PCIE settings. However, for testing purposes, I simply switched the OC Profile to the advanced form ID.

Describe the actual outcome as detailed as possible.

The BIOS appeared to flash successfully using M-Flash, however, clicking any setting in the advanced menu of the modified BIOS caused it to freeze and require a hard reboot. In addition, the BIOS displayed incorrect hardware information, such as zero installed memory, and no devices connected to the MB were detected. Despite these issues, I was able to boot into an operating system and still access M-Flash. To resolve the problem, I had to flash the BIOS again using the stock image, after which I was able to change settings without further issues.

Mark · Answer 1 · Mon Mar 13 2023 06:37:49 GMT+0800 (China Standard Time)

I would like to add to this issue by mentioning that the string "sr-iov" appears in UEFITool NE and an unsupported/non-functional version of AMIBCP that is only used for debugging purposes. However, it does not appear in the editor. I'm unsure if this is related to the issue mentioned above. I've also tried flashing using tools on the MSI website but was met with the same issue. Please see below.

UEFITool NE:

AMIBCP:

UEFI-Editor

Mark · Answer 2 · Mon Mar 13 2023 07:33:52 GMT+0800 (China Standard Time)

I'm going to close this issue and apologize. After trying one more time, everything worked as expected. I'm chalking it down to user error...possibly in the process of replacing the files in UEFITool. However, I still cannot find any setting related to "SR-IOV," as searchable by string.

BoringBoredom · Answer 3 · Mon Mar 13 2023 09:42:12 GMT+0800 (China Standard Time)

SR-IOV is not present in the IFR Extractor output either.
LongSoft/Universal-IFR-Extractor#22 (comment)
This is likely the reason.

Mark · Answer 4 · Tue Mar 14 2023 07:28:40 GMT+0800 (China Standard Time)

Thank you, @BoringBoredom, for the explanation and I apologize again for the false issue. UEFI is fascinating and I'm enjoying exploring it. This tool is incredibly helpful for anyone who wants to avoid lengthy HEX editing and such.

For information sharing purposes: In the rare case that anyone else is searching for the non-existent SR-IOV option on these motherboards, enabling Direct I/O PECI Access Method, Native PCIE, and Native ASPM in the RC ACPI section allowed operating systems to recognize the motherboard as SR-IOV capable. I also enabled ACS but I can't quite remember which section it was in.