Yes, the usage of the UBU tool is very safe and yes, you can let the UBU tool insert the Intel RST(e) RAID ROM v13.2.0.2134 by changing one of the files (although I do not recommend to take any v13 RAID ROM modules for 6-Series chipsets).
The replacement of the Intel RAID ROM version by another better or worse matching version has an effect on the performance of a RAID system, but this effect has nothing to do with the frequency of the replacement.
As you can see >here<, the "classical" Intel RST driver/OROM combo v11.2.0.1006/v11.2.0.1527 gives Intel RAID0 users the best possible performance (even with newer Intel chipsets than your P67).
Any reason why I can’t update my VBIOS to 2180? I remember being able to do so with previous versions. I can only update the EFI ones with the latest. BIOS is for Asrock B85M Pro4.
I did a backup for my PC bios, is an Lenovo IdeaCentre A720, I execute the mod excluding the Microcode, so I flash and everything when well, but My PC actually only support UEFI if I press F12 during booting and select the Sata drive as Legacy or UEFI by default system use "legacy" and will not boot is the OS was installed as UEFI.
question?? How to add the option of selecting the UEFI in my bios. Windows 8.1 pro in UEFI, performance is way much better with UEFI.
AFAIK some ASRock UEFI BIOSes have a space problem with the Option ROM modules. Sometimes it helps, if you change the BIOS module update order.
@ halabibk: Welcome at Win-RAID Forum!
I suspect, that you haven’t restored your optimized BIOS settings after having flashed the modded BIOS. Please enter the UEFI BIOS, choose the "DEFAULT" settings and then open the section "BOOT". There you should find an option to set the "Compatibilty Support Module" (CSM) to "Disabled". After having done and saved this setting, you will automaticly boot in "clean" UEFI mode (provided, that your graphics adapter can be managed by an EFI GopDriver.
@Fernando Hello! You can then tweak as in the first post?
"UBU support UEFI BIOS version Aptio IV for Intel and AMD platforms. UEFI BIOS Aptio V is not supported. (eg on the X99 chipset motherboards), as there is no new version MMTool to work with such BIOS. To work with the BIOS Aptio V use UEFITtool." and "5.5.1028" -> "5.5.1023". This I was wrong.
Unrar the file VBIOS.DAT and put it in the folder \Modules. Note: This OROM VBIOS only for motherboard ASRock B85M-Pro4. !Do not use for other motherboards!
@ Sonix: Thanks for having released and published the new UBU version 1.8.5! According to your changelog you obviously have changed the procedure of updating the Intel VGA ROM (VBIOS) module version. What was the reason for doing that?
Additional remarks: 1) The extraction of Intel VGA ROM (VBIOS) from the BIOS file has to be done with the MMTool, which is part of the UBU tool package. 2) I haven’t yet seen a link to the BMP tool. Where can the users get it?
It’s already done, although I haven’t just copied and pasted your text. I hope, that what I have written is correct and ok for you.
@Fernando This procedure is only for OROM VBIOS Haswell/Broadwell. As you already know, you can not take any OROM VBIOS for Hasvell/Broadwell and insert into the BIOS. So settings are specific to each motherboard. But as has been available BMP, reference VBIOS files and scripts BSF to them, then became possible to transfer the settings from the old version to the new version of the VBIOS. I often had to do OROM VBIOS update, so this has been added to the upgrade procedure. Unfortunately, to fully automate the process will fail, hence this option is designed for advanced users.
The process itself is simple. With the help of UBU look what version OROM VBIOS. For example in 2170. 1. With the help of MMTool extract OROM VBIOS from BIOS file. Usually this VID-DID 8086-402/c02/412/c12. For example we want to upgrade from 2170 to 2180. 2. In a separate folder, copy the files: - OROM VBIOS extracted from the BIOS - script BSF for 2170 - reference DAT and script BSF 2180. 3. Run BMP. 4. Loading OROM VBIOS 2170, and his script BSF, also in 2170. 5. Choose from the menu “BIOS Setting” - “Save All…” and save the settings in SSF-file. 6. In the saved file SSF find and delete one string "STRING $Signon…" 7. Load reference and script files version 2180. 8. Choose from the menu “BIOS Setting” - “Apply All…” and select the previously saved file SSF. 9. After filling in all settings save the file as VBIOS.DAT and copy this file to folder \Modules tool UBU. Everything is now possible to update the correct BIOS. This is a simple procedure and works correctly in most cases.
Collection OROM VBIOS and BMP modification program, the links in >this< post.
Thanks for your reply and for the detailed explanation of the Intel Haswell/Broadwell VBIOS update. There is only 1 question left for me (or am I blind?):
@ ex58: Thanks for the links. Btw it would have been no problem for me to do a Google search for the BMP tool (e.g. >here<), but after having read SoniX’s presentation of the new UBU version 1.8.5 and his guide about how to update the Intel Haswell/Broadwell VBIOS, I thought, that the BMP tool was either linked by SoniX or part of the new UBU package, but I couldn’t find it.
@ all: To make it easier for you I will put a direct download link to Intel’s BMP tool and to the Haswell/Broadwell VBIOS package into the start post of this thread. UPDATE: Done!
@SoniX : Meanwhile I have tried to update the DEV_0412 Intel VBIOS version of my ASRock Z97 Extreme6 BIOS from v1022 to v1028 according your guide. At least I succeeded. Look here:
So thank you very much for having published the new UBU version 1.8.5, which now makes it possibe to update the Intel Haswell/Broadwell VBIOS version.
Note: I compared the hex code of the original file named hsw_1022.dat with my modded VBIOS.DAT file and got the result, that they were identical. Is this ok or should the hex code be different?
