I have tried to update my Supermicro X11SSH-LN4F BIOS with the latest Network EFI Drivers. When I do the update with the Steps 3,1 then I get this messages.
1 - Update Intel 0 - Exit to Main Menu Choice:1
For compatibility of the DevID, it is possible to install up to versions 6.6.04 and/or 1.5.62
EFI Intel PRO/1000 SubGUID 5A411384-868E-4F6E-B955-9454373FD992 OROM Boot Agent GE SubGUID 197FE100-6F80-467D-818A-2DCDF3E19023 Set Device ID 1533 parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah parseFile: non-empty pad-file contents will be destroyed after volume modifications parseFile: non-empty pad-file contents will be destroyed after volume modifications File replaced OROM Boot Agent GE SubGUID 197FE100-6F80-467D-818A-2DCDF3E19024 Set Device ID 1533 parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced OROM Boot Agent GE SubGUID 197FE100-6F80-467D-818A-2DCDF3E19025 Set Device ID 1533 parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced OROM Boot Agent GE SubGUID 197FE100-6F80-467D-818A-2DCDF3E19026 Set Device ID 1533 parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced
EFI Intel PRO/1000 UNDI - 6.3.27 OROM Intel Boot Agent GE - 1.5.86 OROM Intel Boot Agent GE - 1.5.86 OROM Intel Boot Agent GE - 1.5.86 OROM Intel Boot Agent GE - 1.5.86
The Original Output before the Update in Step 3 is
EFI Intel PRO/1000 UNDI - 6.3.27 OROM Intel Boot Agent GE - 1.4.04 OROM Intel Boot Agent GE - 1.4.04 OROM Intel Boot Agent GE - 1.4.04 OROM Intel Boot Agent GE - 1.4.04
When I do an update of the CPU Microcodes with the steps 5, C, U then I get this messages:
Choice:u [Preparing for replacement] Empty GUID: parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced mCode GUID: parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced mCode GUID: parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced [Replacement] mCode FFS: parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced mCode FFS: parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced Empty FFS: parseSection: section with unknown type 00h parseSection: section with unknown type 00h parseSection: section with unknown type 1Ah File replaced Real FIT 01 mCode Offset - FFCDAD18 != FFB5AD30 Fixed - FFCDAD18 mCode Size - 18000 02 mCode Offset - FFCF2D18 != FFB73130 Fixed - FFCF2D18 mCode Size - 17800 03 mCode Offset - FFD0A518 != FFB85930 Fixed - FFD0A518 mCode Size - 18400 04 mCode Offset - FFD22918 != FFB99530 Fixed - FFD22918 mCode Size - 12400 05 mCode Offset - FFD34D18 != FFBB1530 Fixed - FFD34D18 mCode Size - 14000 Backup FIT with Offset
Is UBU Tool not compatible with this kind of BIOS Versions or do I have to do antoher way or replace it manually? I used the Version UBU_v1_70_rc1_fix.
Thank you for your latest 1.70 Rc1 release. It seems to work faster than the old Ubu version. I found it a pleasure to use though have a few questions and suggestion if you don’t mind.
1: I was updating my LAN network drivers and I ended up with this:
Where I did not use to have an ‘EFI Lx Network Killer UNDI’ driver. Not sure why there is even one for Intel Pro/1000 Undi as I have Killer lan ports.
2. The new Ubu will list ‘Other Sata Controller’ or ‘Video OnBoard’ as an option that doesn’t do anything. The old Ubu would not list an item if it did not exist.
3. The Microcode update routine is a little confusing. You have to selected ‘Create FFS with Microcodes’ and from there you have a choice of UEFIReplace or MMTool of which there is an ambiguous brick warning. Perhaps word it ‘Update all Microcode Files’ and add a “Recommended” keyword next to Uefireplace.
I know this a release candidate beta-like software and coding comes before cleaning up the language. Also it would be extremely useful and great if Ubu could create a log file of all the modifications it makes.
Again thank you very much for all of your hard work!
Edit: EFI Lx Network I guess did in fact exist before but Ubu 1.70 says the original rom has an unknown version. Previous older Ubu versions just ignored it for some reason.
@Sylar76 - OK, I get what you mean now! Please send me the stock BIOS or a link to download, and I will look and see if I can figure anything out that will help. Also include your modified setup file, so I can see what you already attempted that didn’t work. And yes, I do agree, having a setup module from the same company on a similar board that does already have this would help, I say same company because they all tend to edit the setup stuff differently sometimes.
That info I linked may indeed help, since it’s about changing CPU count availability, but not in exact same way you need, but similar changes may be required
As to these devices please consider that the guide has been revised, too: [Tool Guide+News] "UEFI BIOS Updater" (UBU) See "additional preparations for certain UBU processing tasks".
Microcode 1C could be from Windows rather than your BIOS. If you open regedit and check HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0 you might see Update Revision and Previous Update Revision keys. The first is the current microcode (1C) and the second is the microcode from the BIOS (presumably 12).
I checked that entry and saw the 1C as Update Revision but didn’t noticed the Previous Version and you are right indeed
So, the Windows version takes place over the other one? Lets say that i download the BIOS from motherboard website and flash it, is it the same as if i updated it with UBU to the 1C Revision?
Windows loads whichever is the newest one of a) the microcode for your CPU from your BIOS b) the microcode supplied by Windows (C:\Windows\System32\mcupdate_xxx.dll). For example, my Skylake system has microcode C2 in the Windows DLL as of KB4100347 and microcode C6 in the BIOS thanks to UBU; Update Revision, Previous Update Revision, and tools like HWiNFO all report that microcode C6 is loaded, since that’s newer than C2.
I just downloaded UBU 1.70 RC1 fixed (UBU_v1.70.rc1-fixed_without-MMTool.rar) from mega.nz and copied MMTool.exe from MMTool 5.02_patched.zip to UBU’s folder, as well as the latest BIOS 3.18 for a Supermicro H8SGL (http://www.supermicro.com/Aplus/motherbo…R56x0/H8SGL.cfm) and the latest MC database. When I start UBU (yes, with admin rights), it can’t find CSMCORE. It is only able to show me the microcodes from the BIOS. What may be the problem here?
Asus was promised to release a bios update, for their remaining Server and Workstation mainboard series (at the above link) for July-31-2018, but they have delayed them to date of August-31-2018.
╔════════════════════════════════════════╗ ║ MC Extractor v1.20.0 r76 ║ ╚════════════════════════════════════════╝ ¦1-306C3- 32 (1,4,5)- 24 -2018-01-21-PRD -0x5C00-0x385020- No ¦ ¦2-306C2- 32 (1,4,5)-FFFF0006-2012-10-17-PRE -0x5800-0x38AC20-Yes ¦ ¦3-306C1- 32 (1,4,5)-FFFF0013-2012-06-14-PRE -0x6000-0x390420- No ¦ Microcodes GUID 17088572-377F-44EF-8F4E-B09FFF46A070
[Update Intel CPU MicroCode] C - Create FFS with MicroCodes E - View/Edit MCUpdate.txt M - User Select only 1 Microcode File [MCExtractor] X - Extract all CPU Microcodes S - Search for available microcode in DB. 0 - Exit to Main Menu Choice:c CPUID 306C3 found. Files\Intel\mcode\1150\cpu306C3_plat32_ver00000025_2018-04-02_PRD_5F430452.bin Checksum correct. Generate FFS with Microcode
From my last question I learned that the message “CSMCORE not found” from UBU means that it is a non-UEFI capable BIOS file, correct? Now I opened the latest BIOS A68DYC09.BSS for a Biostar A68I-350 DELUXE R2.0 (http://www.biostar.com.tw/app/en/mb/intr…ID=618#download) and while UBU shows this messsage, it also finds EFI drivers. Why are EFI drivers within a non-UEFI BIOS?
@Lost_N_BIOS I need update current Haswell microcode (306C3h 24h ->25h) and insert microcode for Xeon E3-1265L V4 Broadwell with eDRAM (40671h, latest microcode 1Eh). I am not sure about existing EFI GOP/VBIOS module (5.0.1023/2166) - it may also need to be updated.
I don’t need preproduction microcodes (306C1h and 306C2h) - you can preserve it, update it or delete it (depends on free space).
And if anything, CH341A flash programmer is only $3