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

Zitat von quetzalin im Beitrag #2780
1
2
3
4
 
-->> 02 mCode Adrress - !!!FFD33BF0!!!
....
Address 01 mCode + Size 01 mCode = Address 02 mCode
-->> 0xFFD1C3F0 + 0x00017800 = !!!0xFFD33BF0!!!
 

If the addresses match then all is well.
If the addresses do not match, it is necessary to correct the value of the address in _FIT_.

You have the address has not changed, it is not necessary correct anything.


[quote="pipes80, post:2780, topic:30825"] what is Z_cpu.ffs? there is an hex value different from my x99 soc Champion bios inside [/quote] These are temporary file that are used for the correct replacement microcode files.

@Fernando
would it be possible to costumize the UEFI BIOS Updater (UBU) for Apollo Lake mainboards?
I’ve just built a new HTPC with a Apollo Lake Mainboard ASRock J4205-ITX which works great.
Many thanks in advance for your answer.

@RoughBoy :
Since your question is UBU related and only SoniX as the creator of the tool is able to answer, I have moved your post into this "UBU Discussion" thread.


BIOS v1.10
Unfortunately UEFIFind and UEFIExtract can not handle the BIOS.


They can. There is a problem with APL SPI images where the last BIOS volume overlaps the start of the next SPI region which is called DevExpansion (UEFITool shows it as Reserved1 as it was called before APL). That’s an AMI/Intel source code issue and for some reason the OEMs and/or AMI/Intel have not noticed or don’t care enough to fix it. The system works because it just so happens that no data are written at the overlapped section or the last BIOS volume actually ends before such overlap, but a proper parser like UEFITool fails because of the wrong sizes. Check the discussion that I had with CodeRush three months ago on the subject with the equivalent solution. So fix that problem and UBU should work via UEFIFind/UEFIExtract at some extend (SoniX has not added APL support other than universal LAN modules). Other than that, it might not be easy at this point to mod APL SPI images due to some new security implementations, BootGuard 2.0 etc. If you can recover from a bad flash then test, otherwise stay away from APL modding for now.

@SoniX
@CodeRush and
@all on UBU Discussion thread.

I am trying to get to grips with the BIOS modding procedure for an Asus X99-Deluxe BIOS 3402 and have been re-directed from the “Manual AMI UEFI BIOS Modding” discussion forum having been re-directed by Fernando

@PC_Pilot :
I am neither the author of the UBU tool nor do I have an Intel X99 chipset mainboard. Nevertheless I have tried to answer your questions according to my knowledge.
If you want to be sure, whether your summary regarding the usability of the UBU tool for X99 mainboard BIOSes is 100% correct, you should better ask SoniX than me.
He is the creator of the tool and knows the best what it can and what not. To be sure, that he reads your questions, please post them into the UBU Discussion thread.

Zitat von PC Pilot im Beitrag #149
b) The Legacy Option ROMS shall require a full manual procedure again using the UEFI Tool.
NB. I would appreciate/welcome some clarification in regards to these ‘manual’ procedures as my present understanding may be muddled??
CodeRush, the creator of the UEFITool and our BIOS Guru, has promised a long time ago to write a guide about how to use his tool, but until now he obviously didn’t have the time to do it.
Nevertheless there is a short guide, which may help you. It is written by our Forum member sinders about how to update the Intel RAID ROM of an Intel X99 ASUS mainboard by using the UEFITool. You can find the short guide >here<.

Perhaps you can verify my understanding in respect of updating the EFI modules using the UBU Tool:

(i.e.) Option 1) for Intel Chipset SATA RAID Controller - DEV_2822, Option 3) for both LAN Controllers (Intel Ethernet Connection I218-V - DEV_15A1 & Intel I211 Gigabit Network Connection - DEV_1539) plus Option 7) for the CPU MicroCodes update together with any other module (eg. NVMe??) you suggest as being available and useful to update.

I would very much appreciate your comments concerning my summary from the linked post above and would also like to consult your expertise as to how best (ideally step by step) to update each of the following Legacy OROMs

IRST RAID for SATA & AMI NVMe Driver
Intel Gigabit Undi
Intel Pro/1000 Undi
CPU MicroCodes (if Manual Procedure necessary)

I appreciate from Fernando’s above comment that you have likely not had the time to draft the desired step by step guide so I apologise if my post seeks to resurrected the issue!

In any case, all help, advice and assistance is very much appreciated.

Many thanks
PC Pilot

EDIT 1 by Fernando: Moved into the correct UBU Discussion thread (the other thread is reserved for SoniX’s UBU update announcements)
EDIT 2 by Fernando: To enhance the chances, that SoniX and/or CodRush get knowledge about your post, I have directly addressed this post to them.

@PC_Pilot :
Since this is the UBU Discussion thread, I have moved your post here. The other thread is reserved for the guide and SoniX’s announcements of a new UBU version.

@SoniX

Hello :slight_smile:

Intel 0.0.15 EFI Gigabit Undi

Intel Lan Gigabit UNDI 0.0.15.zip (112 KB)

@SoniX

Hello :slight_smile:

Here is a odd one, Intel RST 15.5.0.3279 only efi driver, actually the full build number seems to be 15.5.0.32794.
I have not tested it yet.

Intel RST RAID 15.5.0.3279.zip (90.9 KB)

@SoniX

Hello :slight_smile:

Intel SKL/KBL VBIOS 9.0.1049

8086-0406 Intel Skylake-Kabylake VBIOS 9.0.1049.zip (39.3 KB)

Is UBU project dead?

What lets you think that? Do you expect each week a new version?

New Year’s vanity.

Happy New Year everyone!
Health, happiness, love and prosperity.

:slight_smile:

You too, Sonix, happy 2017!

@SoniX

Hello :slight_smile:

Intel SKL/KBL EFI GOP Driver version 9.0.1061

Gop1061.zip (38.8 KB)

(Realized I may have posted in the wrong area previously.)

Currently, when using UBU, I’m seeing a few options for my LAN OROM, originally:
LAN OROM PXE and EFI UNDI - Intel, RTK, BCM, QCA
OROM Intel Boot Agent GE - 1.3.72
EFI Intel PRO/1000 UNDI - 5.5.23

And the provided update paths:

1 - Update Automatic Mode
- OROM LAN Intel BootAgent CL 0.1.10
- EFI LAN Intel Gigabit UNDI v0.0.15
2 - Update Force Mode for Intel
- OROM LAN Intel BootAgent GE v1.5.62
- EFI LAN Intel PRO/1000 UNDI v6.6.04

"Automatic Mode" sounds like the option I’d want to go with, but I notice the devices don’t really match up. The current BIOS has GE and PRO/1000 - which matches “Force Mode”… I’m assuming I’d want to stick with Force Mode here?
(This is for an ASUS Rampage IV Extreme with an Intel 82579V adapter.)

EDIT: And now I’ve found a previous thread by Fernando that has me more confused: Which OROM for Intel PRO / 1000 82579V LAN?
It looks like at one point, only the CL option was available? That would leave one to assume that path would work…

Thank you-

@Lurkios :
The UBU tool is able to detect the Intel LAN Option ROM and EFI modules, which are within the BIOS you have opened, and will give you correct informations regarding available newer and matching Intel LAN modules. So there is nothing to worry about the update of these BIOS modules.
Just for our information: The LAN modules of the BIOS are only relevant, when you use the "Wake-on-LAN" feature.

Previously, GE and PRO/1000 were universities for chips 82759/i217/i218 and i210/i211/i350 up versions OROM Boot Agent GE v1.5.62 and EFI PRO/1000 UNDI v6.6.04
Now Intel has divided:
OROM Boot Agent GE and EFI PRO/1000 only for i210/i211/i350 etc
OROM Boot Agent CL and EFI Gigabit for only 82579/i217/i218 etc



Ah - that’s exactly what I was looking for, thank you for explaining the reasoning.

@SoniX :
Any chance you can upgrade the NVMe driver?
I noticed the body sizes are different comparing X99 to Z270 asus boards.
Is there any version number to report?

EDIT by Fernando: Moved into the correct UBU Discussion thread and added personal address to the UBU author