Fernando. I am facing another issue. I installed Intel RST(e) RAID ROM v12.9.0.2006 and its Satadriver. So, I have into bios the satadriver option but when creating a RAID I can not select any disk by pressing X or other letter. It just flickers but not select and even create the RAID. It happens even with Hard Disks or SSD's
To solve this I return to a non UEFI boot and created the Raid with my SSDs and the Hard Disks Raid by Ctrl+I and returned to an UEFI boot.

To sum up do you think it may be this combination of Z68 and v12.9.0.2006 and I should use v11.2.0.1006/v11.2.0.1527? And Is there TRIM support for v11.2.0.1006/v11.2.0.1527?

Hello @All!
Who knows what the CPU microcode for Hasvell most optimal for overclocking?
Since recently installed 19 CPU microcode, but it is not really suitable for overclocking.

Fernando. I did the Raid0 with the two Kingstons and all worked well besides TRIM that does not seem to be working even with the Universal Sata drive inserted correctly. I checked with the tool TRIM check that shows TRIM is not working even after several tests.

The ssds alone installed TRIM shows working with the tool.

Is that normal the the tool does not show TRIM into raid working? I know that TRIM is only officaly supported by the next chipset generation not in Z68 but the UNiversal drive is there for this, right?

I think it is worth getting this second SDD and install in my laptot rather creating a RAID0 with them in my PC. I guess I'll get the desired performace by that way and let a SSD's raid0 for a next upgrade where TRIM is supported. What do you think?

I require much higher vcore on 19 than prior microcodes for 4770K.

Zitat von jasonsansone im Beitrag #530

---

I require much higher vcore on 19 than prior microcodes for 4770K.

---

@SoniX

Marvell is yet again high in the sky. I have checked the latest BIOS for Z97 Classified posted by stasio here and it appears Marvell has no meaning of naming convention. They have the same version for both the AHCI and RAID driver, without given them a clear tag in the header, like Intel does. I mean, how hard is it to add "Marvell RAID SataDriver" or "Marvell AHCI SataDriver" at the top of EFI module, plus given them a different number branch, to know one from another? Right now, the only way is to search for "Marvell RAID" inside the EFI. It would appear that the AHCI ffs is for 9172 and similar controllers, while RAID ffs is for 9192, 91A2, 9230 and similar. You said someone tested 1.1.0.1007, which is a RAID EFI driver. Do you remember on what board and controller was that, did AHCI worked? Don't know if you should offer a separate AHCI and RAID driver or offer just the latest RAID.

The two modules are 4953F720-006D-41F5-990D-0AC7742ABB61 and 4953F720-006D-41F5-990D-0AC7742ABB62. Also attached a new Extractor with your ideas and a few bugfixes, the rest is the same mess. For quick extraction of microcodes I would recommend to run Z.version.bat and run "bios.rom icpu" or "bios.rom acpu". If there are duplicates, it means that there are more than one microcode ffs module. I have seen Asus BIOSes with 3 different modules that are also doubled, meaning 4-6 microcodes ffs modules. You will get some false positives, but they are easily spotted by the weird date.

@lordkag

Thanks for the info!
I had a suspicion that Marvel is not so simple. And looking at the BIOS from EVGA, these suspicions were confirmed. Indeed, in the BIOS may be two EFI-module, by analogy AMD. One module for AHCI and a second module for RAID,
The next version of UBU, will have to make additional checks to determine the type AHCI or RAID.

PS I made ​​some changes in the utility DrvVer. Now she lets you watch the version in EFI modules - LAN Intel. Realtek and Broadcom, and SATA Marvell ..
And much to ask, please do not use more utility OROMVer. Instead, the utility made ​​FindVer, which allows more flexibility to set parameters for the search versions.

Edit: Meanwhile announce UBU 1.6.0 version as it is.

Zitat von SoniX im Beitrag #535

---

New UEFI BIOS Updater v1.6.0
Change:
1) Update DrvVer v0.6.
2) Add OROM AsMedia SATA 106x v3.70.
3) Add OROM JMicron SATA JMB36x v1.08.01.
4) Folder "OROM" renamed to "Modules".
5) Folder "SPUP" has been moved to "Modules".
6) !* Added ability to update OROM VBIOS Haswell.
7) Changes in the script BAT-file.

!* - to update OROM VBIOS Haswell, first use the BMP program to modify the desired version. Then the modified file rename VBIOS.DAT and put it in the folder "Modules". After that will be available to update OROM VBIOS Haswell. OROM VBIOS Haswell files are not included in the package, as for each motherboard have their individual settings.
All you need to create your VBIOS.DAT here.

---

Chances are that the version 3.xx for later controllers AsMedia. Guess the chip can have additional marking with the letter A.

Zitat von Pacman im Beitrag #538

---

@SoniX
New microcode for Haswell:
Date: 2014/05/23
MC ID: 0326C31A
CPU Id: 06C3
Revision: 1A

---

Hi SoniX and Fernando,

Using Asus X-79 Deluxe with Bios 0701 (newest). Though it is x79-chipset the board comes with RST 12.7.0.1936 OROM and EFI SATA Drivers. Not the RSTe Drivers you can find on predecessor P9X79 DELUXE. In the beginning the UBU tool worked fine updating these drivers, e.g. 12.7.0.1936 to 12.9.0.2006. For some time past, don't know the exact version when changes happened, I get some error and in the following the tool offers the RSTe drivers only. Even if I wanted to update to these drivers, it won't work. May be you can check and make it work for me again
in future version - highly appreciated. Thank's a lot to you both for great work!