@tistou77 did you rename it to mmtool_a4.exe? not as mmtool.exe ?

@ektorasdj

Indeed, after looking in the file UBU.bat, I renamed the file in mmtool_a4, but I had an error while updating
I then used mmtool 5.0 and it's good (5.2 before and renamed in mmtool_a5, but not supported according to the UBU.bat file, I believe)

On the other hand, when updating the microcode, I no longer have the option M, but the option R
The R option does not use MMTool ?

The update of the RSTe module still does not work



Thanks

UBU v1.71
MMTool only needed to replace microcodes (on AMI Aptio 4 and V) and OROM (on AMI Aptio 4).
In all other cases, MMTool is not required.

Replacing IRSTe/VROC (x299) is not yet available. I'm working on it.

@SoniX
Ok thanks

Only use MMTool v5.0 ?
Not 5.2 version with UBU 1.71 ?

And R option for microcode, use mmtool ?

Thanks

Zitat von tistou77 im Beitrag #4939

---

Only use MMTool v5.0 ?
Not 5.2 version with UBU 1.71 ?

---

Zitat

---

And R option for microcode, use mmtool ?

---

Auto selection.

Does anyone have a updated custom BIOS for the X99 Deluxe II or at least the latest OROM/EFI SATA/LAN for it?

*NM, created a custom bios.*

Hey @Lost_N_BIOS , I guess you were right...

I edited the file, changing the 01 to 00 and it doesn't say Invalid Image anymore... But says Invalid MAC Address LOL

:(

What to do here now?

Suppott VROC/new IRSTe

IRSTe/VROC (global - all version 3-6)
5.005.005400650020003.002E003.002E003.00
 
 

VROC with VMD vers 5-6
560052004F00430020007700690074006800200056004D004400200054006500630068006E006F006C006F006700790020003.002E00
(Intel package as VMDVROC_1.efi)
 
????? VMDD - Volume Management Device Driver - no version
(Intel package as VMDVROC_2.efi)
56006F006C0075006D00650020004D0061006E006100670065006D0065006E00740020004400650076006900630065002000440072006900760065007200
 
 

@SoniX
For VROC how to do it ?

And I have the information NVMe (like on your screen) and the files are present in tmp directory after scanning but it is not possible to update ?

Thanks for your help

@DarkPoe - where do you see invalid MAC address? Did you edit the MAC Address or GbE region? What was your source BIOS file, downloaded from Gigabyte? Upload your mod BIOS, and give me your MAC ID, I will put in there for you.
But, there may be some issue with your mod BIOS, since this should not be required at all if you are using stock BIOS image from Gigabyte (Modified) and are flashing via Qflash, since Qflash will leave current valid MAC ID in place.

@Lost_N_BIOS:
I am using the one I posted before ( http://download.gigabyte.us/FileList/BIO...s-elite_f7d.zip )
No, I did not edit any MAC or anything... Just updated the RST and Intel LAN ROM/drivers like this:

EFI IRST GUID 91B4D9C1-141C-4824-8D02-3C298E36EB3F
parseFile: non-empty pad-file contents will be destroyed after volume modifications
File replaced
OROM IRST  SubGUID D46346CA-82A1-4CDE-9546-77C86F893888
parseFile: non-empty pad-file contents will be destroyed after volume modifications
File replaced
 
     EFI IRST RAID for SATA     - 17.2.0.3790
     OROM IRST RAID for SATA    - 17.3.0.3758
Press any key to continue . . .
 

For compatibility of the DevID,
it is possible to install up to versions 6.6.04 and/or 1.5.62
 
EFI Intel Gigabit SubGUID 4953F720-006D-41F5-990D-0AC7742ABB60
parseFile: non-empty pad-file contents will be destroyed after volume modifications
File replaced
OROM Boot Agent CL SubGUID 50339D20-C90A-4BB2-9AFF-D8A11B23BC15
Set Device ID 0x15BB
parseFile: non-empty pad-file contents will be destroyed after volume modifications
File replaced
 
     EFI Intel Gigabit UNDI     - 0.0.22
     OROM Intel Boot Agent CL   - 0.1.13
Press any key to continue . . .
 

Description . . . . . . . . . . . : Intel(R) Ethernet Connection I219-LM
Physical Address. . . . . . . . . : E0-D5-5E-E4-08-02
 

@DarkPoe - Thanks, I will check it all out. Since you are using stock BIOS and Qflash, you should not receive any message about MAC ID even if it's changed from the stock default (invalid one, 88:88:88:88:87:88 = placeholder)
I can directly put in your correct MAC ID in place of the default placeholder, but this should not be required at all. You did not say, where are you seeing/getting Invalid MAC message?

* Edit - the attached image does not have the Qflash block removed?? So, either you edited wrong thing, or you didn't upload correct final file?
I do not see any issues and GbE region is untouched from stock. Try the mod again, without editing the Intel PXE rom, unless you are booting from LAN then this does not need updated anyway, if you are, then OK still lets test without this change to see if this is the issue.

@tistou77

The replacement of VROC (new brand IRSTe) has not yet been done. I'm working on it.
But I do not understand the purpose of VROC with VMD. How it works and what is the connection with another VMDD driver.

AMI NVMe is a regular driver. It is not updated.