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

[SoniX]

@lordkag

That Intel Lan sample was indeed 3.4.12, but for 10Gb. The strange part was that the pattern was also found in the header. What where the chances for that to happen?
I had a look at 10Gb and 40Gb. For 10Gb we can use "49006E00740065006C00280052002900200031003000470062004500" = "Intel(R) 10GbE" unicode; for 40Gb "49006E00740065006C00280052002900200034003000470062004500" = "Intel(R) 40GbE" unicode. I tested this on all my samples and all Intel_Lan_CD/PREBOOT.exe releases, it always works.
For 40Gb you can use [start_match - 0x23]. Samples are attached.

And I’m confused in determining 10Gb or 40Gb of normal. I will make an additional check, and then by mistake, you can not replace the module.

Are you sure that you want to add Intel GOP ValleyView support, which is for Bay-Trail = laptops/tablets? Because it is a mess, with versions as 7.0.x, 7.1.x, 7.2.x and probably 7.3.x soon and so on. I use a bunch of wild guesses in Extractor, but there is no reliable method of detecting the full version. And to this the x86/x64 separation and you get a wild picture. Samples attached.

Of all the files GOP ValleyViev I only 7.0.xxxx. I would think, to introduce support for a replacement or not to enter

I haven’t yet looked at the code of UBU 1.9.0 or 1.10, but I noticed two errors:
- Broadcom UNDI is not updated, still at 16.2.2
- you need to change the lines from 106-109 to the ones bellow. You need %%~nxi because %%i will give you the full pathname and you are trying to use a local variable as a global.

• LAN Broadcomm UNDI added later.
  - It seems to work, but check again.
  
  Thank you very much for the good advice.

[SoniX]

Test the updated tools.
UEFITool v0.20.1
UEFIExtract v0.4.1
UEFIPatch v0.3.1
https://github.com/LongSoft/UEFITool/releases/latest

[SoniX]

@ex58

Zitat von sinders im Beitrag #1361

---

Thanks ex58 for posting the Intel CPU Microcode for the X99 platform. How do you find out what the Intel CPU Microcode version is your BIOS you're using contains?
I take it none of the modding tool available right now are able to mod the Intel CPU Microcode within the BIOS of the X99 platform?

MMTool 5.0.0.0007

---

@sinders
Not so simple.
What motherboard? Attach the BIOS.
Important. There SPI-programmer?

[sinders]

@SoniX

Not so simple.
What motherboard? Attach the BIOS.
Important. There SPI-programmer?

As I have previously mentioned on the board, I have a ASUS Rampage V Extreme X99 board.

Here is the latest BIOS to date for the board.
http://dlcdnet.asus.com/pub/ASUS/mb/LGA2…E-ASUS-1001.zip

I don`t have a hardware SPI-programmer as yet thought I can still flash my modded BIOS using the BIOS USB
flashback feature because I have tested this out myself on my board when modding the BIOS with a
newer Intel RAID ROM module.

Thanks in advance for the help and feedback.

EDIT by Fernando: Unneeded quoted text deleted (to save space)

[SoniX]

@sinders
Ok. Wait half an hour. Now gather FFS-files.

[sinders]

@SoniX

@sinders
Ok. Wait half an hour. Now gather FFS-files.

Thanks mate for having a look into it for me. I have read that it is best to update to latest Intel CPU Microcode for your platform if you can.
The advantages of using a up to date Intel CPU Microcode is it can give a more stable running system and better overclocking.
I take it this is true about the advantages of using a up to date Intel CPU Microcode?

EDIT 1:
The Intel CPU Microcode the above official BIOS contains is Microcode : MU063F0229 and is what my board is using for my system.
I fount out what my Intel CPU Microcode version is by using SiSoftware Sandra.
That is the Intel CPU Microcode version SiSoftware Sandra is showing for me for my system.

[SoniX]

@sinders

I take it this is true about the advantages of using a up to date Intel CPU Microcode?

Well, it’s every man for himself decides.

Ok. Take the first test. While changes in
- OROM IRST 13.5.0.2164 (2 modules)
- OROM Intel LAN PXE GE 1.5.61
- EFI IRST 13.5.2164
- EFI Intel LAN UNDI GE 6.4.13

If fashion sew and everything is working fine, the next test will change the CPU microcode. Waiting for results.

[SoniX]

@sinders
As the results?
I already have everything ready for the next test.

[sinders]

@SoniX

@sinders
As the results?
I already have everything ready for the next test.

Well the BIOS flashed without issues I think but something is not right as the system is experiencing crashing issues with the
modded BIOS which possibly means something not like what has been changed or something not right with the mod.

The Lagacy OROM IRST 13.5.0.2164 and the OROM Intel LAN PXE GE 1.5.61 seems to be working fine
thought I am not sure how to test the others.

[SoniX]

@sinders
So work?
If OROM work, then to test the EFI-files need to go to the full UEFI mode. But I think that they, too, will work without problems.

Ok. We turn to the second test. All too saioe but upgraded CPU microcode:
- 06F0 - 17
- 06F1 - 14
- 06F2 - 2D

Warning! If your motherboard does not start, then roll back to a working version.
It is waiting for the result!

Edit: File deleted.

[sinders]

Is that a fresh mod you have done with just the CPU microcode upgrade?
That would be best because it would rule out issue that may be caused with the OROM modules being changed.

[SoniX]

This mod contains updated OROM, EFI and microcodes. It is necessary without updating the OROM and EFI?

[sinders]

@SoniX

This mod contains updated OROM, EFI and microcodes. It is necessary without updating the OROM and EFI?

Is it possible you could do a fresh one with just the microcodes updated?

[SoniX]

Ok. Only microcodes updated.

[sinders]

@SoniX

Ok. Only microcodes updated.

The system boots fine with microcode updated BIOS mod and the new microcode seems to be working.

@SoniX
I think that will do for the moment. I will test the stability of the new microcode and post here whether I notice a difference or not and if I experience any issues I have not had before since the microcode was updated.
Thanks again SoniX for your time and help with this mod.

[SoniX]

@sinders
Stop!
Check the third test. Since FFS file microcode has 2 status! BOOT-YES and BOOT-NO. Who was stitched with the status BOOT-NO. In the original BIOS status BOOT-YES.
This can be seen by entering a command in the command line
"mmtool <BIOS file> /p". MMTool 5.00.0007.

Edit: This BOOT-YES as in original BIOS.

[sinders]

Sorry I don’t know what you mean by Stop!.
Do you mean ok we’ll stop for now?

EDIT: OK. I will test the third mod and let you know if the system still boots fine and if the microcode still seems to be working.

[SoniX]

So, what has been done.
Taken BIOS files from Gigabyte and Asrock.
With MMTool5 been updated microcode CPU and extracted FFS-file "as is".
With UEFITool v0.20.1, was replaced two files in the BOOT-volumes.

2 finished attaching the file to X99 with different statuses BOOT.
I do not know how important this status. But I think that it is better to stick to the original.
2 status in FFS flle with microcodes.

LGA2011v3_Microcodes.rar (90.7 KB)

[sinders]

I have tested your third mod and the system seems to boot just fine. I take it I should keep to using your third mod for the longer
testing of the updated CPU microcode since you said it is better to stick to the same as the original which is BOOT-YES?

[SoniX]

I think it’s better to stick to the original.
Thank you for tests.