Hi,

Does anybody know if can be added more voices to the setup guid 899407d7-99fe-43d8-9a21-79ec328cac21 ?

What I mean is this:

I've successfully added Coffee Lake support (with HT enabled) to a MSI laptop bios which supports only quad core CPUs.
Now, the 8700k cpu is properly detected by bios and OS, but under CPU Configuration I can manage only 4 cores (like a quad core cpu)
instead of 6.

Extracting the guid 899407d7-99fe-43d8-9a21-79ec328cac21 and viewing also with AmiBCP it has indeed only strings for 4 cores and
I can't add more strings in any way.

I've tried, with Universal IFR Extractor, to find the hex values for the turbo options for 4 cores and I've manually added new hex values
for the other 4 cores (in order to have support for an octacore CPU) but when I try to reinsert module with UefiTool or MMTool and open
bios again with AmiBCP it says that ROM has incorrect setup tables and it seems to be messed up, so I ended saying that the Setup GUID
899407d7-99fe-43d8-9a21-79ec328cac21 can't be extended with new options, but only mod the existing ones.

I think the only way is to obtain the setup guid from a similar motherboard having native 8 core support, but if someone has or can share
some tips it will be very appreciated.

@SoniX

Ok, I have read page 278, fine then. Thank you very much for replying me....

I don't know if it is a concern, but - as with all 1.70 versions before - only Ivy Bridge microcode will show up in MMTool's 4.50.0.23 "CPU Patch" tab (this MMTool version only used for checking the result - not for the modding procedure!) if I use rc1 to update all microcodes included in my (Gigabyte Z77) AMI Aptio 4 BIOS - no matter which of the four update methods is applied (the last two stall anyway). If I check the same mod in MMTool 5.0.0.7 all updated microcodes will show up though.
By modifying v1.69.17.4 (Sel1155.bat) I was able to update both Ivy Bridge and Sandy Bridge microcodes to the latest versions (20/2E) - and they both show up in MMTool 4.50.0.23.
I consider compliance with MMTool 4.50.0.23 as a "quality gate" for AMI Aptio 4 BIOSes. That's way I've preferred to (successfully) flash the BIOS modded by using "enhanced" v1.69.17.4.

@Sular76 - maybe this is the guide you need - [GUIDE] Fixing HT for Coffee Lake CPUs on Skylake and Kaby Lake motherboards (Z170, Z270)

@Lost_N_BIOS

What I mean is under Power Configuration (AmiBCP) where I can set only 4 cores (like a quad core) instead of 8.

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.

Sonix,

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:

EFI Intel PRO/1000 UNDI - 6.6.04
EFI Lx Network Killer UNDI - 1.1.0.10
OROM QCM-Atheros PXE - 2.1.1.5
OROM QCM-Atheros PXE - 2.1.1.5

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

Zitat von davidm71 im Beitrag #4282

---

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.

---

Zitat von davidm71 im Beitrag #4282

---

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.

---

When i download the BIOS file from my motherboard website and check it using UBU, i can see this:

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).

thurask,

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?

PS: Thanks Fernando for the spoiler tag, my bad

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?

Here are some screenshots: https://imgur.com/a/h5Rbw5c

Zitat von BlackArchon im Beitrag #4289

---

latest BIOS 3.18 for a Supermicro H8SGL

---