@yyjdelete :
Welcome to the Wn-RAID Forum!
I don’t know the reason why the Intel CPU MicroCode update via the option “U” didn’t work for you. You should better ask @SoniX.
Unfortunately I cannot test it myself with my ASRock Z97 Extreme6 mainboard, because the board died 2 years ago.
Regards
Dieter (alias Fernando)
@yyjdelete
The problem is in UEFIReplace. We decide here
@hoffer
OROM Lan is located in GUID 365C62BA-05EF-4B2E-A7F7-92C1781AF4F9, as with BIOS Aptio V, then updating with available means is not possible.
Fixed a check against a false choice GUID.
@SoniX :
Thank you very much for your new UBU version v1.70.b18-Dev. It is absolutely admirable how many new options you have recently implemented into the UBU v1.70 platform!
Before I am going to test the UBU v1.70.b18-Dev and to replace the current pictures of the UBU Guide, I need your statement to >this< post.
Thanks in advance!
@Fernando
Thank you. That’s just the problem does not become less, with each time there are new ones.
@ALL
Looking for BIOS files from mobo containing controller Marvell SATA. Interested BIOSes on the platform Aptio V.
@SoniX Thanks for the v1.70b18 update, now the only thing missing from v1.70b18 from the v1.69 version in the ROM’s I typically update is the update for dev 4391:
v1.69:
1 - AMD OROM and EFI Nodules
OROM AMD AHCI 4391 - 3.0.5
Has option to update to:
1 - AMD OROM and EFI Nodules
OROM AMD AHCI 4391 - 3.3.2.0
v1.70b18 has no update options for that dev.
v1.70 STOCK MAIN PAGE:
1 - Disk Controller
EFI AMD RAID - 1.0.0.49
OROM AMD RAID MISC 4392 - 3.2.1540.6
OROM AMD RAID MISC 4393 - 3.3.1540.11
OROM AMD AHCI - 3.0.5
EFI AMI NVMe Driver present
v1.70 STOCK UPDATE PAGE:
[Current version]
EFI AMD RAID - 1.0.0.49
OROM AMD RAID MISC 4392 - 3.2.1540.6
OROM AMD RAID MISC 4393 - 3.3.1540.11
OROM AMD AHCI - 3.0.5
[Available version and Update]
R - <br /> EFI AMD RAID - 1.0.0.49
EFI AMD Utility - 1.0.0.49
O - <br /> OROM AMD RAID MISC 4392 - 3.3.1540.19
OROM AMD RAID MISC 4393 - 3.3.1540.19
0 - Exit to Main Menu
I did notice its also missing the update all option, but that’s a LAZY mans option really and not priority.
Hi, I have found a small typo error in latest (v1.70b19 Dev) version of UBU_dev.bat
Line 1056:
echo (Version 3.80 only fir 3.xx)
@SoniX :
Yesterday I have tested all options of the UBU tool v1.70.b19-Dev by using again the ASRock Z97 Extreme6 BIOS v2.70. Everything worked fine for me. Thanks again for having developed and optimized this brilliant and easy to use tool - congratulations!
Since this UBU version seems to be the first final one of the v1.70 platform, I have just completely revised the UBU Guide and inserted brandnew screenshots. I hope, that everything is ok for you. If not, please let me know it.
@all:
Any suggestion for improvement of my UBU Guide is much appreciated!
I just attempted to apply an update to my motherboard’s AB0 firmware version, and every change I make, it reports:
parseFile: invalid data checksum 5Ah, should be AAh
@SoniX to reiterate what @Fernando mentioned, I’m facing this issue with my Haswell board with dual Intel NICs.
It’s either one or the other. I cannot select both NICs within the selection menu.
@kode54
This is a message from the UEFIReplace, which file does not have the correct CS. If you are not sure, use MMTool.
@SimpleTech
Strange, but changed the label. Fixing.
And why do you need a second variation? If you have 82579/217 or 218, then it is better to use the first one.
@Sonix
with the last "Dev19_fixed" the Network option for Intel nic update does crash (bios asus 3902 for Sabertooth X99), previous UBU version did not crashed.
Fixed.
@kode54 :
Welcome to the Win-RAID Forum!
Your error message has nothing to do with the work of the UBU tool.
Please open the original (= untouched) BIOS by using the UEFITool. If you will get the same error message (what I expect), you can be sure, that I am right. In this case the related BIOS has been wrongly composed by the mainboard manufacturer, but it may work properly nevertheless.
Regards
Dieter (alias Fernando)
YES, tested it for Sabertooth X99 as well P8Z77, all is OK with "UBU_b19_Dev_fix1" just released. Thanks again Sonix.
@SoniX :
The problem regarding the update of the Intel LAN i218 chips, about which I had reported >here< and >here< is still present in your latest UBU version.
I just have tested the “fix1” variant of the UBU_v1.70.b19 with my test BIOS. The update of the Intel LAN modules works, when I choose the recommended option 1 for the i218 chip, but the UBU tool still replaces the original LAN EFI module “Intel PRO/1000 UNDI” by an Intel Gigabit UNDI" module and the original LAN Option ROM “Intel Boot Agent GE” by an “Intel Boot Agent CL” one.
Is this correct?
Again: When I choose the (not recommended) Intel LAN update option 2, everything seems to be ok (I get updated “Intel PRO/1000 UNDI” and “Intel Boot Agent GE” modules.
Here is the related picture:
@Fernando
UBU does everything right.
This topic has been discussed more than once.
Briefly I repeat.
Initially, for all chips 82579/210/211/217/218/350 and the like, there were only files OROM BA GE and EFI PRO/1000.
Latest version 1.5.62/6.6.04 compatible for all chips on Device ID.
After the output of the i219 chip, there was a separation of the OPOM and EFI into 2 streams.
And now the support and compatibility of Device ID looks like that
- for 82579/i217/i218/i219
– OROM BA CL and EFI Gigabit
– List of Compatible Device IDs \bacl.txt
- for 210/211/350
– OROM BA GE and EFI PRO/1000
– List of Compatible Device IDs \bage.txt
@SoniX :
Thank you very much for the clear and detailed explanation. I didn’t know that and obviously have missed the related discussions.
Sorry about the confusion!
Hello!!
Is there a timeframe on when Intel RAID oROM and EFI will be added back in? Seems that is all that is missing now.