Don’t you see the "IRST TRIM-in-RAID Addon" option? It should look like shown here:
If not, I recommend to open the UBU\Modules\IRST\12_9 subfolder and to replace the file named SataOROM.bin by the file named SataOrom.bin, which you can find within the TRIM6\12_9 subfolder.
@ Fernando
For X79, too, must make access to TRIM-files?
Edit:
Strange. All are silent. I thought that for the X79 is not necessary, and made only for 6-series chipsets.
So i did befor you it wrote, 
And with the other usb-stick system run with new orom.
New Windows is installed.
Thanks!!! For your help.
Thomas
That is, for Haswell processors, microcode version 19 is the best for overclocking?
@ SoniX:
Users with an Intel X79 Chipset system and an Intel RAID0 array may not really need a TRIM modded Intel RAID ROM or EFI RaidDriver module, but the insertion of a TRIM modded module does not harm the system at all.
According to Intel only Intel Chipsets from the 7-Series up natively do support TRIM in RAID0. The X79 Chipsets belong to the C600 Series Chipsets, which are at least 6-Series ones.
On the other hand do the Intel RST RAID ROM modules v11 and up contain the TRIM in RAID0 flag, which indicates, that they do support this feature (look >here<).
Hello. Thank You for the work done. I will put a message in front microcode version 19 as "Best overclocking"
@ Fernando
Thank You. The next version UBU, will be able to Trim-in-Raid0 for the X79 chipset.
@Fernando
I’m quoting you to clarify something related to this. Let’s say i update those RAID modules to version 13.1.0.2126 as you mentioned. Do they support TRIM? Are they TRIM ready?
My question comes after i’ve read some posts of yours and your members here yesterday, i got confused. I wanna make sure that if i update them i won’t get in trouble if someday i want to change to RAID mode.
It depends on the Chipset of the user’s mainboard and on the RAID configuration:
By modded variants do you refer to your Modded Intel AHCI and RAID Drivers or to this T option in UBU’s?
My chipset is from 7 Series, so i assume i won’t get in any trouble if i update to your suggested version, from what’ve understood.
SoniX
please, have you a answer for this Problem, see Picture, a little confused for me, i mean ID15A1 are right and not was ASRock or ubu…
Open your BIOS in MMTool.
This picture is all manufacturers. On my Asus Z87-Plus (i217-V)
DavID in OROM 1503, in OS Win7 - 15b3. But it is not critical and is not a problem.
In UBU setting OROM taken from data CSMCORE.
Edit:
If we look the rules of filling DevID, the manufacturers are wrong. In any case, everything works without problems.
…works without Problems, yes ~99%, when i set Settings default, no Problem, when set secure boot, Default Bios or modbios with ubu, Bios can not connect to asrock Server (search to new Bios), have here (Forum) a modbios P2.30 with ID15A1 and have no Problem btw. this Error notification, had already want to ask you earlier to this Erratum, but forgotten.
@ morpheus67
You use CSM or UEFI mode?
Edit:
If you enable Secure Boot, then you use UEFI mode. In the UEFI mode, the OROM are not used. Then your problem is in the file EFI LAN.
What is your version of EFI LAN?
Which version UBU you used for modifying?
@lordkag
I have a question. Necessarily it is necessary to update module HiiDataBase from AMD RAID?
It rarely is, in BIOS and I think that it is better to leave as is.
Hi
I’ve been using the UBU tool for a while and just been lurking these forums.
Not sure if it’s been reported already but I got a bug with the UBU 1.29 beta 1
It won’t update the LAN EFI rom. Is working in UBU 1.28 beta 6
I’m using Windows 10 and the bios is for ASUS Maximus VII Ranger
Thanks for a great product 
I know this problem. The problem will be fixed in the next release.
But there is a serious problem.
We can not understand the work EFI LAN driver version 0.0.07 on chips 82579/i217/i218. If the version 0.0.07 is not working, it is necessary to return the version 6.6.04. But so far no one checked.
On my motherboard Asus Z87-Plus it looks like this:
Well honestly I don’t know much about what that does. I kinda just update it because the option is there
What kind of tests can be done to help?
My bios shows the same as yours with the 0.0.07 . Only the PCI Device Id is different.
In short, my suggestion is to keep it and update it when it is found. But here is the long story. As you can read here or here or EDK2 implementation, the file has nothing to do with AMD or RAID. If AMD needs to add a RAID menu to the UEFI setup screen, if should probably use handlers like EFI_HII_DATABASE_NOTIFY_ADD_PACK and EFI_HII_DATABASE_NEW_PACK. Why it doesn’t do that, I don’t know. Maybe the implementation of UEFI at that time was too buggy or the results were not predictable on all platforms. You can see that they also added SCSIBus and SCSIDisk, which normally should be compiled by OEMs. So keep all the files that AMD provided and update them when found. As you have observed, HiiDatabase is rarely found and it is even marked as optional by AMD.
The trick part is that Intel platforms also have Hiidatabase, SCSIBus, SCSIDisk - so you must be careful when you update them. I have added the known GUIDs to Extractor, but I can’t say for sure which are the good ones. The safest bet is to search for AMD RAIDx64, it always has the same GUID C468B382-4550-4909-AD57-2496141B3F4A, so only in this situation you can update the other 3 EFI drivers. This is what I did in Extractor to remove the false positive for both AMD and Intel, as I noticed that Hiidatabase, SCSIBus, SCSIDisk have little to do with Intel or AMD.
In the next version UBU will be able to choose the version EFI Intel LAN
Hi SoniX,
I have been using the UBU tool for quite a while now and I have WDS and use PXE to install my OS’s on my Desktop machines.
Recently have done a lot of testing into why my Gigabyte boards, some of them installed in UEFI mode and some in Legacy mode. I seemed that the Z97 modded ones with Atheros would boot from UEFI fine but the Z87 modded ones with Intel would not, only Legacy would work.
Your very latest UBU v1.29 Beta1 fix (Beta Version) however fixed all that by not updating the EFI part of the Intel code, going back over some of the previous versions, yes both the v0.0.07 and v6.8 definitely did not work for i210/i217 board, did not think to try any earlier, just the built in EFI Intel PRO/1000 UNDI - 5.1.00 worked the best so far.
Anyway, sounds like all the above reflects the same as what you have noted, keep up the great work 
