@ mjgr33n:
Welcome at Win-RAID Forum and thanks for your feedback.
Regards
Dieter (alias Fernando)
I have this test machine with this BIOS: https://downloadcenter.intel.com/downloa…ng%2FBL0160.BIO
The model and brand of the mainboard is: Intel DH67BL. I tried using “UBU_v1_28_BETA_2” and it does detect it properly and I can update the BIOS components inside. In the OP of the UBU tool it says that it CANNOT be used for Intel mainboard BIOSes. Why is it working with this BIOS then? It does say it’s an AMI Aptio 4.
BIOSes from Intel, Insyde and Phoenix not supported. Since they are not AMI Aptio
Hi Fernando, I just tried the new tool UBU v1.29 (official version) and unfortunately for GA-Z87X-OC Force BIOS F10 which has both Intel i210 and i217 that Intel EFI LAN PRO/1000 UNDI v6.6.04 does not work, so in this instance the skip updating EFI UNDI is very useful, not sure if you can put better warning in this section of the tool, but might be useful for those of us with dual Intel LAN boards.
Thanks again )))
Ah ok. So in that case, the when I upload the file to UBU and it detects it, that is just an erroneous result?
EDIT by Fernando: Unneeded part of the fully quoted text removed (to save space)
Can you please quote the text passage within my guide, where you found this statement?
I will prepare for you a few options. You can do several tests with different versions?
I will prepare for you a few options. You can do several tests with different versions?
Sure, happy to
@ mjgr33n
Test 1 GA-Z87X-OC Force BIOS F10b
Mod only EFI LAN Intel PRO/1000 v6.6.04 without DEPEX Section
Verify whether the presence DEPEX section.
Report only ‘working’ or ‘not working’.
@Fernando
I’m very sorry, I had a typo on that post. It was supposed to be this:
In the OP of the UBU tool it says that it CANNOT be used for Intel mainboard BIOSes. Why is it working with this BIOS then?
This is why the second sentence of that paragraph says “why is it WORKING with this BIOS then?” so as to contradict the first sentence and hence my confusion. Why does UBU detect the Intel BIOS properly if it is known to be not an AMI APTIO BIOS?
Working
What is different about this, what is DEPEX?
@mjgr33n
Hmmmmm…
Ok. Download the official version 1.29.
Replace file UBU.bat.
Make mod a version of Intel LAN 6.6.04.
Flashing mod BIOS and tell the result.
Edit:
I forgot to attach a file.
Edit2:
In the attached script, I disabled the addition DEPEX section.
@Sonix
It does seems that v2.8 BETA 2 does detect the modules within the Intel BIOS but v2.90 doesn’t. v2.90 only detects the CPU Microcode.
Which boards have the EFI LAN module inside their BIOS? Do only the modern boards have this?
Strange. Indeed it opens.
1) All OROM under different GUID. And for this we need to write additional script. The standard AMI Aptio all OROM are in the same repository ÑSMÑORE, what makes the update much easier.
2) The problem is that flash the modified BIOS from Intel is very problematic.
@Sonix
I understand. With that said though, are there other alternatives to have Intel mainboard BIOS modules updated?
At your own risk, you can manually update the dates of your modules using UEFITool. Other options for working with Intel BIOS I do not know.
It worked perfectly
EDIT by Fernando: Unneeded parts of the fully quoted text removed (to save space)
It worked perfectly
Rubbish then…
Ok.
Do it again mod, but using only original UBU.bat v1.29.
Flash and the last time check. We must make sure that it does not fail to assemble FFS-file.
Intel .BIO have a digital signature that gets broken once you mod the image. You cannot mod such files, only extract some components using a tool such as PhoenixTool. No modding.
Got it.
And just curious, why isn’t MEI updating included in UBU? No pun intended here.