[ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions

BIOS/UEFI Modding BIOS Modding Guides and Problems
3881

@JanCerny :
The answer given by karakarga is not correct - it is vice versa:
The patched MMTool v5.2.0.24 is usable with AMI Aptio V and many AMI Aptio IV UEFI BIOSes, whereas the unpatched v5.2.0.24 is only usable with AMI Aptio V BIOSes (if you try to open an Aptio IV BIOS with the unpatched variant, you will get an error message, that it is not an AMI Aptio V BIOS).

3882

Hi forum,

is it safe to flash a msi laptop ge60 2pc with an UBU modded bios if i ONLY update Microcode?

Greetings from Germany

3883

@Mod76 :
Flashing a modded BIOS into a Mobile System is never absolutely safe (especially not, when the CPU Microcode has been changed) and should only be done, if it is absolutely required.
Before you are starting this adventure, I recommend to ask the manufacturer of your laptop for a BIOS update.

3884

@Fernando :
Could you please update first post?

MMTool v5.00.0007 released on 2014 - for Aptio IV

1
 
SHA-1: a37872d43b01dc39a28bb086ffb066c2f5bf735a
 

MMTool v5.02.0024 released on 2017 (unpatched) - only usable with AMI Aptio V
1
 
SHA-1: fba82bd83c603700e6763ed8a9c5633980822c21
 

MMTool v5.02.0024 released on 2017 (PATCHED) - usable with AMI Aptio V and many AMI Aptio IV UEFI BIOSes
1
2
 
SHA-1: 8e54ac68de355e1031527b89c0560ae1c9c8c508
 
 
3885

Done!
Thanks for your suggestion and for posting the SHA-1 values of the different MMTool variants, which are usable with the UBU Tool.

3886

Adding 2 more…

3887

DB r63

3888

@whatnot

There is also version v3.26 it’s SHA1 checksum can be added as well.

SHA1:05d81e32820d6618f0b77990fa376764615c5bd8 : MMTool v3.26.exe

3889

Got an error message reading in an Aptio V BIOS from an AMD board with v1.70 a16: "‘aet’ is not recognized as an internal or external command, operable program or batch file."

I searched for “aet” in the batch file and I think there’s a typo on line 143: “uefifind body count 4147455341 bios.bin>nul && aet amd=1 && goto amdextr”. “aet” here should probably be “set”.

3890

@ Ver Greeneyes

Version 1.70 in the Alpha stage, so many small bugs.
But thank you for the information.

3891

Hey all
I have Hero VII Z97 MB.
In UBU i get these for Intel Lan:

LAN OROM PXE and EFI UNDI Intel, Realtek, BCM, QCA

1 - Update Automatic Mode
- OROM LAN Intel BootAgent CL 0.1.13
- EFI LAN Intel Gigabit UNDI v0.0.19
2 - Update Force Mode for Intel
- OROM LAN Intel BootAgent GE v1.5.62
- EFI LAN Intel PRO/1000 UNDI v6.6.04
0 - Exit Main Menu

Enter number:
My original bios comes with:
LAN OROM PXE and EFI UNDI - Intel, RTK, BCM, QCA
OROM Intel Boot Agent GE - 1.5.47
EFI Intel PRO/1000 UNDI - 6.0.03
So, im guessing the option 2 (Force Intel) is the right one? Its the one that follows the original BIOS version scheme.
Or am i wrong?
Thanks.

EDIT by Fernando: Post shortened by using “spoilers” (to save space)

3892

@ karserasl
If Intel ChipLAN OnBoard 82579/217/218/219 update Option 1
But you can use option 2 if the chip is 82579/217/218

3893

Hm, Thanks for the help SoniX

My NIC is Intel(R) Ethernet Connection (2) I218-V
So you suggest Option 1?

3894


Yes.

3895

Hello, @SoniX .

I have a few questions about Intel CPU Microcode:

1. What’s MPDT ? What does it do ?
2. My BIOS (MSI Z170)have 2 Microcode module in 2 volume and first has MPDT_BOOT_NO , second has MPDT_BOOT_YES . Can I add Microcode to both volume ? Do I need replace first MPDT_BOOT_NO to MPDT_BOOT_YES ?
3. Can I Insert Microcode to 2 or 3 volume and edit _FIT to point to them ? Will it work ? Which MPDT to use ?

Seems like mCodeFIT cannot handle some situation :

1. _FIT is located after Microcode module.When I add new Microcode , the address of _FIT changed. And I need to edit the VolumeTopFile to point to new address of _FIT.
2. Microcode module is located in 2 or more volume.
3. Sometime I found mCodeFIT didn’t change the size of FIT Header when I add or delete Microcode .

Best regards.

3896

@SoniX :
Could you please add support for recognizing NvmExpressDxe_Small. Lack of support seems to cause confusion among users in the [Guide] How to get full NVMe support for all Systems with an AMI UEFI BIOS thread.

Although I’ve removed all character strings to conserve space, a private protocol GUID specific to this driver could be used for identification:

uefifind body list 0D85CB4033203646BA1466790571757E bios.bin


Note that the current signature used for identifying “Clover Team NVMe Driver” is matching all drivers derived from any TianoCore NVMe driver:
L"NVM Express Driver\0NVM Express Controller\0\0"

Considering that Clover is using the EDK2 NvmExpressDxe unmodified, you may want to consider using a more generic name for that signature.

Thank you.

3897

@ Ethaniel
For 1-3 variants of drivers CT NVMe it is possible to make corrections, but for "Small" variant it is not clear what sequence of bytes to take.

3898

@SoniX :
Please use the following pattern to identify NvmExpressDxe_Small that is a GUID I have generated specifically for this driver:

0D85CB4033203646BA1466790571757E

3899

@ Ethaniel
Use to determine the GUID is not true. Since someone can set their GUID,
But I’ll see what can be taken as the basis for the definition of the “Small” option.

3900

@SoniX :
This an internal protocol GUID compiled into the .efi file so cannot be modified as simply as the FFS GUID.
Note that for the FFS file I just used the standard EDK2 NvmExpressDxe GUID that is not specific to my version.