Hello, another blind guy here!
I was trying to mod my Gigabyte H81M-S2H. And I stumbled upon something odd, so I just want to confirm it’s alright.
I modded latest bios from Gigabyte website.
When I used the MMTool, it said the “big” version exceeds the volume size (for both “as is” and “compressed” FFS options). The small version went through though. But when I verified it using UEFItool, I found one pad-file missing.
Then I tried modding the file using UEFItool, followed the instruction, inserted the small version, verified again - the pad-file was missing again. Tried both UEFItool 0.28 and 0.25.1, same results.
The odd thing is… I also tried to insert the “big” version using both UEFItool versions and it didn’t say any warnings about size (like the MMtool did). And when I verified the final files, the pad-files seems to be in correct places.
But after saving the moded BIOS, I reopen it to check, and it shows that the “NvmExpressDxe_5.ffs” module is not the last one, in fact, it swaps position with the empty named module just above it (the one with “00010018” bytes size and GUID “05CA01…”).
I don’t know anything about BIOS, but looking at the source and output files, I think the “NvmExpressDxe_5.ffs” file should be inserted at offset “006E0000”, the start of Volume free space, is it correct?
This is my calculation, based on the report from MMTool and from UEFItool user interface:
So I try to create the file myself here, by copying “NvmExpressDxe_5.ffs” file to the start of volume free space. File size remains the same, and volume free space size down an amount equal to the nvme file size. e7760ims.480.self.fd - Google Drive
Both MMTool and UEFItool shows Okay, but as I dont know anything about BIOS, so I am not sure. Pls help me to validate it.
Thanks for the links to the BIOS variants. Meanwhile I have checked them.
Here is my evaluation: You can flash the BIOS, which was modded by the AMI Aptio MMTool.
The NVMe module has been correctly inserted by the AMI Aptio MMTool as undermost “DXE Driver” without moving/deleting/inserting any Pad-file.
Good luck for the flashing procedure!
Please read the start post of >this< thread before you start doing that. You have to rename the BIOS file.
It is the undermost “DXE Driver module”. A Pad-file doesn’t count.
All modules of the compressed DXE Volume have been resized, because you have inserted an additional module. Since the total size of the BIOS must not be changed, the BIOS Tool enhances the compression of the DXE Volume and its components.
No, it is a “Raw” module (neither a “DXE Driver” nor a “Freeform” module.
You can verify it yourself by opening the BIOS with the UEFITool.
The AMI MMTools don’t show Pad-files.
You are right - my guide was not exact enough regarding your quoted sentence. To avoid any future confusion I have now replaced the words “undermost module” by the words “undermost DXE Driver module”.
I hope, that all your questions have been answered by me and you can now flash the modded BIOS.
I was lucky enough to find an experimental/incomplete uefi bios and this great thread for my old msi p45 motherboard. I know have revived an old pc, added a nvme boot drive with uefi windows thanks to this guide . I wonder if i could increase ssd speeds (my pcie adaptor supports 4 lanes i could use 8 lanes on this board’s pciex 16lane). Thanks, and happy new year!
PCIe lanes are the physical link between the PCIe supported device and the processor/chipset.
Assuming a common NVme 3.0 x4 disk:
You’re NVMe disk will only uses x4 lane bandwidth, regardless the adaptador mechanical design or PCIe slot mechanical design higher than x4.
Even so, as on your motherboard the PCIe generation is not 3.0 (8.0G/Ts), it will only use 2.0 (5G/Ts) x4 maximum speed.
You cant “squeeze” more from a old P45 chipset PCIe2.0
What you have now is the NVMe possible miracle on this motherboards generations and cant never
achieve the performance provided on the technology used in latest chipsets.