In this case I don’t recommend to insert any Intel RST RaidDriver module, which belongs to the v14/15/16/17 platform.
The one I was trying to insert was the latest v13.5.0.2164 (GUID 90C8 which matches the GUID of the current one)
@Noezy :
The GUID of the complete RaidDriver doesn’t matter, if you use the latest UBU version and put the desired RaidDriver.efi file (without GUID header) into the Files\intel\RST subfolder.
A small note for names:
- versions 3-5 as "Intel RSTe <number> SATA}SCU}sSATA Driver"
- versions 6 as "Intel VROC <number> SATA}sSATA Driver"
@SoniX :
Does that mean, that I shall rename all Intel RSTe v6 platform RaidDriver modules, which I am offering within the start post of this thread?
@Fernando
Oh no. :))
I just do not understand. In fact, the 6th version is RSTe, but someone at Intel wanted to rebrand. :))
@Fernando @SoniX
Intel SKL/KBL/CFL GopDriver 9.0.1085
Intel RST 17.2.0.3790 EFI & Legacy OROM
Intel SKL-CFL GOP 9.0.1085.zip (36.8 KB)
17.2.0.3790I.zip (167 KB)
@all:
Update of the start post
Changelog:
- new: “pure” Intel RST EFI “RaidDriver” v17.2.0.3790 (without header)
- new: “pure” Intel EFI “GopDriver” v9.0.1085 for Skl+Kbl+Cfl iGPUs (without header)
Notes:
It has to be tested, whether the new GopDriver really supports SkyLake and KabyLake iGPUs.
Thanks to Pacman for the source files.
Good luck!
Dieter (alias Fernando)
GOP newer than 9.0.1080 are not suitable for Z170 chipset, I suggest that this should be put in the OP with the appropriate GOP…
@gpvecchi :
Thanks for your report.
Did you test it? If yes, what happened?
I have customized the start post regarding this point. Is it ok like it is now?
Not personally, but many reported it. In effects, 1082 and 1084 are Coffee Lake dedicated, and they need a most recent VBT in bios.
Intel GOP Driver 9.0.1082-1085
At the moment we have 2 theories.
1 - to work with SKL/KBL, a configured VBT version 2.21 is required
2- in GOP Driver disabled support Device ID SKL/KBL.
To test these theories, you need 2 identical motherboards from ASRock, with different chipsets, but with the same name. Example:
Z170/270 Pro4 vs Z390 Pro 4
It is important that the Z390 contains the last version of the GOP Driver.
Why ASRock?
I noticed a long time ago that ASRock from almost the same models does not reconfigure VBT for GOP Drivers and in OROM VBIOS.
Hi,
Can anyone confirm or deny weather the intel RST raid rom modules are manufacturer specific for a given mainboard? For example has anyone had trouble on an Asus Z270 upgrading the raid efi driver past 15.5 to 15.9 without issue such that the build in raid console in bios is functional and allows you to create raid arrays?
Thanks
@all:
Update of the start post
Changelog:
- new: “pure” Intel RST EFI “RaidDriver” v17.2.5.4046 (without header)
Notes:
It has to be tested, whether this RaidDriver version supports Intel 100-/200-Series Chipset systems.
Thanks to Pacman for the source file.
Good luck!
Dieter (alias Fernando)
@davidm71
I have done a bit more testing (build/destroy RAID array in CSM mode then in EFI mode) with all the matching v15, v16 & v17 modules and these are my results on a Gigabyte Z170.
Working OROM & EFI matching modules;
17.8.4.4671
17.8.3.4687
17.8.2.4684
17.8.0.4507
17.8.0.4460
17.8.0.4438
17.5.5.4401
17.5.3.4203
17.5.0.4136
17.0.0.3713
17.0.0.3713
17.0.0.3592
16.5.0.53439
16.5.0.3492
16.5.0.3487
16.3.0.3377
16.0.1.3339
15.9.3.3408
15.9.0.3194
15.8.0.3109
15.7.0.3054
15.7.0.2925
15.5.1.3017
15.5.0.2875
15.5.0.2813
15.2.2.2775
15.2.0.2754
Non-working OROM & EFI matching modules;
17.7.0.4404
17.5.2.4317
17.2.5.4046
17.2.0.3790
17.0.0.3720
16.7.0.3513
16.0.2.3402
16.0.1.3397
16.0.0.3155
I had one anomaly with 16.0.0.3155 where the OROM was fine but the EFI module caused failure to POST.
@chinobino ,
I am beyond impressed. Good work!
However I think there might be manufacturer specific roadblocks as the Asus bios integration could cause issues in my case. Only one way to find out.
Anyhow wonder which one gives you better performance. Age old question.
Also love to know how you pulled off a 9900K running on a Z170 board!
Updated my Z270-WS to 16.5.0.3492 without issues. I had to rip them from an Asus Z390-WS motherboard because of my fear there may be manufacturer specific tweaks in there. I know not proven.
Also because the Z390-WS had matching Orom and efi driver versions which I have trouble finding on this forum matching pairs.
I know no one cares about ORoms anymore but I get OCD over it.
Thanks
Which matching OROM/RaidDriver pairs didn’t you find here and why should it be “pairs” (only 1 of them will be used)?
I know only one will be used but I am a little obsessive compulsive I suppose. Thank you.
Best performance for me is so hard to tell now because;
1) CPU microcodes for Spectre/Meltdown caused noticeable I/O performance loss on SKL/KBL/CFL since Feb 2018
2) Drivers and OROM/EFI modules are now released more frequently than ever before and sometimes out of step, making testing difficult
3) Windows 10 updated to new build every 6 months or so and also cumulative updates that have introduced many problems
4) Benchmark programs have been updated over the years - are previous results even comparable? (I have benchmarks from 2015)
5) BIOS updates effecting I/O performance
On the support page for my Z170 motherboard Gigabyte has listed 17.2.0.1009 WHQL for RAID/AHCI and until Intel releases a driver that no longer supports Z170 then I will continue to just keep updating with every new release and trying to match with the relevant OROM/EFI modules.
Maybe once support stops (I never expected +4 years support for Z170) I can go back and test to see which one is best with whichever Windows 10 build I am currently using.
I would also really like to know if certain manufacturers put in ‘roadblocks’ as you say - I tested all the EFI modules without a GUID header and had POST failure with 7 of them but no clue as to why.