Updating the P8Z68-V Pro bios v3603 with UBU v1.70b8 went fine, now running microcode 2E. I’ve used UBU v1.69.17.2 to update everything but the microcode, then used the resulting file in UBU v1.70b8 to update the microcode, and finally flashed the file in DOS via bupdater.exe. FYI, i’ve modded the bios two times, 1st time with UEFIReplace and 2nd time with MMTool, and the resulting files are bit-identical.
Updating the MSI X299 SLI Plus v1A with UBU v170b8 still doesn’t look good to me. When using MMTool, i get the same “Error in saving” error in MMTool as @lettermand99 reports. Using UEFIReplace does work, but produces tons of errors messages while doing its work (see attached screenshots). I haven’t flashed the updated file yet.
In BIOSes MSI x299, the PEI volume, where the container with microcodes is located, has a fixed size, and any change thereof leads to a brick.
There are two ideas, but they require testing. [Method 1] The first idea is to delete all microcodes, and put new ones in the "Empty" that is in DXE-volume. [Method 2] The second idea is known. With the help of MMTool, first remove all the microdots, and then insert new ones. But you will not be able to return all microcodes if their total size is larger than that already exists in the BIOS.
PS I hope that the method 1 will be a working option.
Add: These methods are available in UBU v1.70 b12.
U - with UEFIReplace - All models A - with MMTool - Asus x299 or if brick with "U" [for MSI x299] M1 - Method 1 - Replace "Empty" M2 - Method 2 - Delete/Insert microcode
The 4D for Skylake-X (x299) increases the TJMax from 105 to 110°C, and thus the temperatures of the cores, is also increased by 5°C I stay with 49 for the moment
U - Used UEFIReplace - All models A - Used MMTool - Asus x299 or if previous option makes a brick. [Only MSI x299 Seties TEST] M1 – Method 1 - Replace “Empty” - Please report M2 – Method 2 - Delete/Insert mCode 0 - Cancel Choice:a [Preparing for replacement] Empty GUID: parseFile: invalid data checksum 5Ah, should be AAh File replaced mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh File replaced mCode GUID: parseFile: invalid data checksum 5Ah, should be AAh patchVtf: PEI Core entry point can’t be found in VTF. VTF not patched. File replaced [Replacement] mCode FFS: File replaced mCode FFS: File replaced Empty FFS: parseFile: invalid data checksum 5Ah, should be AAh File replaced Premere un tasto per continuare . . .
1 - Update Intel 0 - Exit to Main Menu Choice:1 EFI Intel PRO/1000 GUID 48392194-D155-4567-9AAF-FA805BAEEC6C parseBios: one of volumes inside overlaps the end of data File replaced EFI Intel Gigabit SubGUID 9006872D-3A86-4BAE-A2F0-E527B9D7119E parseBios: one of volumes inside overlaps the end of data File replaced OROM Boot Agent CL SubGUID 50339D20-C90A-4BB2-9AFF-D8A11B23BC15 Set Device ID 156F parseBios: one of volumes inside overlaps the end of data File replaced OROM Boot Agent GE SubGUID 0FDD6564-FF41-4C31-8BC4-376130E5939A Set Device ID 15A0 parseBios: one of volumes inside overlaps the end of data File replaced
@bleili : Welcome to the Win-RAID Forum and thanks for your report! The error message “parseBios: one of volumes inside overlaps the end of data” is obviously caused by a faulty original BIOS and not by the UBU tool. You can check it by opening the original BIOS by using the UEFITool. I bet, that you will see the same message. Regards Fernando(alias Fernando)
Do we have an idea when feature parity will be reached with v1.70 to v1.69?
While this is great for some newer boards, its BLOODY MAGIC for older ones, AMD specifically, and the only thing I was able to update with my AMD board is the Killer, none of the rest of the AMD rom was able to be updated (storage, my main concern).
As of now, I have to run it through v1.69, first, then v1.70
I tried new option M1 from ubu b12 to update MSI X299 bios - new microcode was added in a new “Vol 1” but the old microcode was also left in the bios in the original “Vol 4”. :
I was able to manually delete the old microcode from “Vol. 4” using MMTOOL, leaving only the new microcode, but I have not tried flashing it yet. I will flashing it if you think it’s probably correct (all microcode in new Vol. 1, all old microcode in Vol. 4 deleted.)
@Net7 Do you have a motherboard for AMD? If the Aptio 4 platform, then use 1.69 to upgrade the RAID. If the platform Aptio V, then send a link to the BIOS.
all 4 of my boards are v4 AMD boards (990fx/A88X), but its not only the RAID thats updatable with v1.69 and not v1.70, AHCI/NVMe as well, basically, ANYTHING storage related is no-go, literally the ONLY thing v1.70 works for on v4 platform bios is the LAN update for Killer
thus I understand I will have to use v1.69 first, and thus my question, is it in the works, or will I need to continue to use both versions to get all updates for the foreseeable future
@lettermand99 It’s strange. All microcodes must be removed from the 4th volume, and new ones are added to the 1st volume. s there something wrong. Send your BIOS.
@Net7 I did not quite understand. And what exactly you can not update?
Version 1.70 in the beta stage. In the near future, will be added support for AMD on the platform Aptio V. For the Aptio 4 platform, I’ll add gradually.
When I see that editing manually, I always update both volumes with matching code. I’m not sure if that is correct thing to do, or if even necessary, but BIOS works when doing that way. Does it also work as a standard editing method to only put new in single volume and remove all from any secondary volume?
– intel-ucode-with-caveats/ – This directory holds microcode that might need special handling. BDX-ML microcode is provided in directory, because it need special commits in the Linux kernel, otherwise, updating it might result in unexpected system behavior. OS vendors must ensure that the late loader patches (provided in linux-kernel-patches) are included in the distribution before packaging the BDX-ML microcode for late-loading.
NEW! Intel Microcode Update Guidance pdf also released!
I already understood this situation. In your case, for i211, version 8 will not work, only compatible 6.6.04.