what will happen when i insert a new ROM (from an other mobo that supports Ivy) into this mobo ?
@SoniX
Good news and very bad news. New Intel RAID - 13.2.0.2134 as OROM and EFI in X99 BIOS. The bad news is that CSMCORE is removed and MMTool stopped working, fails to extract. UBU fails at extracting CsmDxe (new CSMCORE), but also at :d0cpu, all because of MMTool.
Check in module A0327FE0-1FDA-4E5B-905D-B510C45A61D0, they are packed as FreeForm subtype GUID.
Added:
Intel Lan EFI in new GUID 9006872D-3A86-4BAE-A2F0-E527B9D7119E, but old 6.1.14 version; Atheros in new GUID 93761039-4C9A-42FE-AE98-5DD5652F931E, but still 1.1.0.4. I would say that you can re-add Atheros EFI to UBU. Atheros latest is 1.1.0.4 and has “Atheros” in ASCII, while BitFoot latest is 1.1.0.3 and has “BitFoot” in ASCII. But if you tested and found problems, ignore this advice.
Also found a new EFI Shell in this BIOS. It is bigger and possibly newer than the one found in Asrock and MSI. But it comes from an AMD board, so I don’t know if it will be different because of this.
Intel RST RAID 13.2.0.2134.rar (140 KB)
UEFI Shell.rar (515 KB)
@lordkag
You’re a little late, but still Thank you very much. 
Pacman me in the morning announced a new version of IRST. I have already gathered modules for UBU, now testing.
Add:
This new structure BIOS - APTIO V. It will no longer CSMCORE module.
MMTool version 4.50 with such a structure is not working correctly. Alternatively use UEFI Tool and UEFI Extractor.
With EFI LAN Qalcomm (Atheros/Bitfoot) there are some nuances, so they are removed from the pack.
Add2:
UEFI Shell.rar
UEFI_Shell_x64 unknown.efi == UEFI_Shell_x64 unknown.ffs
2.31 / 4.654 / Current runnig mode 1.1.2
File size grows, and the version does not change. Strange as that…
Inside archive are swapped file extension.
UEFI_Shell_x64 unknown.efi is ffs
and
UEFI_Shell_x64 unknown.ffs is efi
@ gabiz_ro:
Welcome at Win-RAID Forum and thanks for your contribution.
Regards
Fernando
Is there a working link for the latest UBU 1.6.1?
I have ASUS P8Z77-V Pro with modded BIOS 2104 using UBU 1.5.0 and I wonder which of the latest updates apply to my motherboard. Do they include ASMedia SATA 3.70 OROM? My current ASMedia OROM version is 0951. What about Intel RST SATA 13.2.0.2134 OROM? I currently have 13.1.0.2126. Is there an UBU release that has ASMedia SATA 3.70 OROM? and Intel RST SATA 13.2.0.2134 OROM already included? Could someone link me to it? I see some people here say that ASMedia SATA 3.70 OROM is not compatible with my motherboard and I also see some people posting screenshots of ASMedia SATA 0954 OROM, so maybe the latest ASMeia OROM for my motherboard is 0954? I actually had to update my ASMedia SATA OROM manually using CSMCORE entry, but now I see people posting screenshots of UBU detecting ASMedia OROM’s by itself! Does that mean I no longer have to manually update ASMedia SATA OROM’s from now on?
I would appreciate if someone would clarify all these versions for me and post a link where I could download the latest UBU 1.6.1 or newer! Thanks!
@ MonarchX:
Welcome at Win-RAID Forum!
I try to answer all your questions:
Yes, look into the start post of this thread under "Preparations".
Yes, the UBU tool v1.6.1 offers is, but it will not work for your system.
Maybe the next UBU version will contain it, but I do not really recommand to insert it as long as there are no Intel RAID drivers of the v13.2 series available.
The answer is "Yes!" regarding ASMedia SATA3 ROM v3.70 (it is offered by UBU v161), but will not work for your system. The answer is "Not yet"" regarding the Intel RST RAID ROM v13.2.0.2134.
As I already have written: There are at least 2 working links to the UBU v1.6.1 within the start post.
That is correct. The UBU tool v1.6.1 offers v0.954.
Again: Look into the start post of this thread under "Preparations". There you will find 2 links to the newest UBU version.
Regards
Fernando
@ SoniX:
Thanks for the new UBU v17.0.
I just have tested it with my new ASRock Z97 Extreme6 board and everything worked fine.
Here is the screenshot I took after UBU had done its work:
@ Fernando
Many thanks for your test.
Addded:
In the meantime, I wrote a list of changes [Tool] “UEFI BIOS Updater” (UBU) (45)
Thanks!
The complete changelog is already within the start post.
@SoniX
Beaten again by the ninja of modules. With a dramatic pause and voice: no problem, I understand. Jokes aside, we are lucky to have Pacman on this forum (and SD).
So we need MMTool 5.xx for X99 and later BIOSes. Unless UEFITool will support command lines.
Yes, the UEFI Shell was uploaded in both forms (but mixed extensions, as gabiz_ro noticed), in case you needed only one of them. Next time I’ll upload just the EFI, if that is what you need. Curious that it has the same version as the older one, but probably that one is for Intel and this one for AMD.
About UBU 1.7.0, I have noticed a few typos, if you don’t mind this kind of reporting:
- line 76,77 should be changed for BIOS with odd extension:
) do copy “%%i” “%~dp0”\bios.bin>nul
if not exist bios.bin goto err
(hexfind 01000000A7060200 temp\cpuffs.ffs>nul || hexfind 01000000A9060300 temp\cpuffs.ffs>nul) && set m8=8 && set s1155=1 && set pcpu=SandyBridge/IvyBridge && echo Platform Socket 1155 - SandyBridge/IvyBridge
(hexfind 01000000D7060200 temp\cpuffs.ffs>nul || hexfind 01000000E4060300 temp\cpuffs.ffs>nul) && set m8=8 && set s2011=1 && set pcpu=SandyBridge-E/IvyBridge-E && echo Platform Socket 2011 - SandyBridge-E/IvyBridge-E
hexfind 01000000A7060200 temp\cpuffs.tmp>nul && set m8=8 && set s1155=1 && set pcpu=SandyBridge/IvyBridge && echo Platform Socket 1155 - SandyBridge
hexfind 01000000A9060300 temp\cpuffs.tmp>nul && set m8=8 && set s1155=1 && set pcpu=SandyBridge/IvyBridge && echo Platform Socket 1155 - IvyBridge
…
:mrvlver
...
hexfind 004b1b9291 csmcore>nul && %mmt% /e /l temp\9192.tmp 1b4b 9192
if exist temp\9192.tmp for /f "tokens=* delims=O" %%b in ('findver " OROM Marvell 88SE9192 - " 42494F532056657273696F6E20 14 00 10 temp\9192.tmp') do set verm9=%%b
if exist temp\9192.tmp echo %verm9%
hexfind 004b1ba291 csmcore>nul && %mmt% /e /l temp\91a2.tmp 1b4b 91a2
if exist temp\91a2.tmp for /f "tokens=* delims=O" %%b in ('findver " OROM Marvell 88SE91a2 - " 42494F532056657273696F6E20 14 00 10 temp\91a2.tmp') do set verma=%%b
if exist temp\91a2.tmp echo %verma%
hexfind 004b1b309200 csmcore>nul && findver " OROM Marvell 88SE9230 - " 504349524B1B3092 -21 00 10 csmcore
...
exit /b
Updated bios with 1.7.0: it said that I have latest CPU microcode, but I had 29 version 19, I had to select 28, then again 29 to update to 1B…
What’s wrong? Example EVGA Z97-FTW. 2 almost identical GUID from Marvell modules.
Zitat
- lines 943-963 should be reworked as:
to prevent 9192/91A2 version appearing twice. Please also notice the missing ().1
2
3
4
5
6
7
8
9
10
11
12
:mrvlver
...
hexfind 004b1b9291 csmcore>nul && %mmt% /e /l temp\9192.tmp 1b4b 9192
if exist temp\9192.tmp for /f "tokens=* delims=O" %%b in ('findver " OROM Marvell 88SE9192 - " 42494F532056657273696F6E20 14 00 10 temp\9192.tmp') do set verm9=%%b
if exist temp\9192.tmp echo %verm9%
hexfind 004b1ba291 csmcore>nul && %mmt% /e /l temp\91a2.tmp 1b4b 91a2
if exist temp\91a2.tmp for /f "tokens=* delims=O" %%b in ('findver " OROM Marvell 88SE91a2 - " 42494F532056657273696F6E20 14 00 10 temp\91a2.tmp') do set verma=%%b
if exist temp\91a2.tmp echo %verma%
hexfind 004b1b309200 csmcore>nul && findver " OROM Marvell 88SE9230 - " 504349524B1B3092 -21 00 10 csmcore
...
exit /b
UBU_v170_cor.rar (9.79 KB)
Nothing wrong, it was just cosmetic. Needs to be "echo […] GUID 4331898D- […]" and "echo […] GUID A28F1CD7- […]".
For 9192 you need to avoid "echo […]" part, because it will display both lines. Use set instead. See file attached. It will probably be a good idea to move "hexfind 004b1b9291 csmcore>nul && %mmt% /e /l temp\9192.tmp 1b4b 9192" and ""hexfind 004b1bA291 […]" to line 168, to avoid repeated extraction.
You could add *.BST for latest BIOSTAR files.
Is DrvVer not showing anymore SCU for EFI RAID? It only displays "EFI IRSTe SATA". I mean it is missing SCU word. See this:
check.rar (8.8 KB)
The two links under Preparations are not working for me. Does it work for others? I have no internet problems at all, but http://www.smartredirect.de/redir/clickG…r-quot-UBU.html and http://www.smartredirect.de/redir/clickG…r-quot-UBU.html do not open anything or start a download… http://www.smartredirect.de/ also does not work. I tried the latest Chrome Beta and the latest IE11 on Windows 8.1. I tried to disable AdBlock Plus, but that made no difference. This is why I was asking where to download previous UBU because those links never worked for me in the past and aren’t working now… My ISP is AT&T if that makes a difference…
Could someone please upload to a different location?
EDIT:
OK, I downloaded using a proxy. Are you saying that the very latest Intel IRST OROM/EFI will not work with existing drivers? Then the latest Intel UNDI EFI uses an earlier version that the one I have. Is the one I have really bugged for all who use it or just some people? Does UBU include MEI or ASMedia USB? I guess I should just enable it and find out. I noticed that UBU detects Intel iGP even though it is disabled, but it does NOT detect ASMedia SATA, which is also disabled.
EDIT by Fernando: Fully quoted and text deleted (to save space within this thread)
No, I didn’t write that.
1. When you are running your Intel SATA Controller in AHCI or IDE mode, the Intel RST RAID OROM/EFI SataDriver modules of the BIOS wil not be used at all by your system.
2. As long as no Intel RAID drivers v13.2.x.xxxx are available, it doesn’t make much sense to insert any Intel RAID OROM/SataDriver module v13.2.x.xxxx. The RAID driver version line should match the OROM/SataDriver version line.
I don’t know that.
No, because both of them are using a special Firmware, which has to be flashed separately.
The UBU tool doesn’t look into the BIOS, which is currently in use by your system (it is within the BIOS chip of your mainboard and cannot be seen by the UBU tool). It just looks into any offered UEFI BIOS file and detects the OROM/EFI modules and versions, which are inside the file. You current BIOS settings don’t matter at all!
v1.6.1 has EFI Intel UNDI 6.2.08, but v1.7.0 only shows 6.1.16 for X79 Sandy 3930k Asus Sabertooth BIOS 4701.
