What do you expect from the desired replacement and where did you get the v13 platform Intel RST EFI VMD module?
Edit:
Thank you Fernando for the answer.
But …
First time I had to change Bios,
was when Microsoft stopped Security Updates,
for Win7 x64.
Even though Win10 had inside the Folder of:
c:\Windows\…
some file with MicroCodeUpdate,
The P.C. me : It wasn’t stable.
At some point I put in the P.C. the Bios by Lost_N_Bios
with date: Wednesday, December 16, 2020, 9:48:23 AM
and with “Flash via USB Flashback” .
The P.C. Started.
But it was slower than before…
Even though I went through Win10 x64, from the beginning.
The New M.E. FW: 8.1.70.1590 , did not pass ,
and …
it didn’t go through in the simple, and absolutely correct, way described by: Lost_N_Bios.
(I was too tired to see it:
M. E. FW: 8.1.70.1590 … in bios of P.C. , when it starts.)
But the P.C. it remains slower
and
mainly : not fixed.
Then I started dealing with UBU.
After I had made some Mod Bios
with
EFI Intel RST VMD Driver - 13.2.0.2134
OROM Intel RST for SATA - 13.2.2.2224
…
MicroCodeUpdate them in his way :
C:\UBU\Files\intel\mCode\USR_mCode
_Readme.txt
and
everything else he had… The UBU,
except AsMedia 1061:
and I changed
the New M.E. FW: 8.1.70.1590 … by: Win-Raid.
With UEFiTooL, it was very simple.
((Then … long time ago … I had found :
and some minor differences , [using Hex Editor],
between M.E. FW: 8.1.70.1590 by Lost_N_Bios
and
of: M.E. FW: 8.1.70.1590 , by: Win-Raid.))
I decided to run Original Asus 4805 Bios first,
and with “Flash via USB Flashback”.
and
after : Mod Bios.
But on the first Try
to pass Original Bios 4805 By Asus.
The P.C. It wouldn’t start.
in Q-Code table
Code | Description
00 | Not used
The M/B:
Had Out: 00 .
I bought a new Chip Bios with genuine Asus Bios 4805.
The P.C. Start Immediately.
Then Buy and
a low cost XGecu Programmer.
Flash the Mod Bios to a new Chip Bios,
and the P.C. Start Immediately.
Actually even now, I have the same thing now.
the Set
EFI Intel RST VMD Driver - 13.2.0.2134
OROM Intel RST for SATA - 13.2.2.2224
I think it was the most stable and fastest.
(Irrelevant :
Everything was going well until about two months ago
when it started destroying USB 3.0 sticks
Now [as of today] I have no idea what happened but…
not only does it not destroy them, …
but he also writes them 3 to 4 times faster.)
e.g. UBU does not change (for EFI Intel RST)
User Interface from SataDriver…
If it seems that he has some serious reason, even in
ASUS Original Bios 4805 else writes U.I. and another is in Reality.
There is no way I can change the FW of AsMedia 106x.
Except, maybe MMTooL .
Lately I have been dealing with:
There (in MMTooL) I saw what the:
Insert of AsMedia 106x, it is very simple.
I did it right away [0.951] and saw it on UBU too.
(I haven’t put it on M/B’s Chip yet).
I also found out that the M/B: ASRock X79 Extreme4-M
Has OROM Asmedia 1061_DXE V0.93 Twice
In Positions 611 and 612.
I also learned that ASUS X79-DELUXE uses more Microcode.
And everyone only in Thesis Vol.2
It has CPUID: 306E7 in Bios.
But It Is Not Compatible With Xeon E7.
Thank you all for your help.
You all have my appreciation site.
You are doing a good job.
Without you My M/B … Would not work anymore.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
[Question.]
… or …
[Request] Update of the Intel RST EFI RaidDriver Module
Could someone write to me,
how do i change the :
EFI Intel RST RAID Driver - 12.7.0.1936
with the:
EFI Intel RST VMD Driver - 13.2.0.2134
Only by using MMTool.
Without using UBU or UEFiTooL.
The : EFI Intel RST RAID Driver - 12.7.0.1936
It’s about Bios: ASUS X79-DeLuXe 4805.
https://dlcdnets.asus.com/pub/ASUS/mb/LGA2011/X79-Deluxe/X79-DELUXE-ASUS-4805.zip?model=X79-DELUXE 1
Regards.
Dioskouridis.
Here you have 2 mods of the 4805 CAP version.
The X79DLX.CAP only with new IRST 13.2.0.2134.
The 2nd CAP with IRST, mcodes updated, LAN updated and Marvell updated.
Use ONLY, repeat ONLY if / by the USB Bios Flash Back in correctly functioning.
X79DLX4805mod.rar (8.9 MB)
Regarding the Xeon, nothing to add, as Chinobino has already clarified you.
Hello MeatWar !
You took the trouble to make the Bios for me with: IRST 13.2.0.2134.
I also found a Post that @Fernando (From what I understand) also Agrees.
USB Bios Flash Back Not working properly at all.
But I have a reservation on file, from Original Asus Bios-Chip,
with all the additional elements needed, using the Programmer.
And I can Put them, in your Bios too,
with “FD44Editor . exe” from “github . com”.
Then I convert it to Rom or Bin, and Put it in a Bios-Chip with the Programmer.
Thank you very much for the help, which you offered me immediately.
(It’s not the first time, I’ve learned a lot from your short and meaningful posts).
[My posts: are : Lots of words … and from juice → Chaos.]
But the evolution of the human species is based on Greed! (Not in Ingratitude!).
And I’m also afraid of it, because even in FW change with instructions and
software from the same (native)
the trial of the company, the device may be damaged.
(It’s happened to me before).
The … SataDriver_12_7_1036
It hasn’t changed …
This is how bios that I made in the past with UBU have remained.
But not even Asus (on 4805) Changed it to : SataDriver_12.7.0.1936.
But I know well … what works perfectly.
If I change it
User Interface
then it changes
and
the Compressed … but,
I haven’t put it in the Chip-Bios, because I don’t know:
Will it work correctly, or not at all.
As I have written before I had put in the P.C. the Bios of Lost_N_Bios.
Everyone liked it, but it doesn’t fit on my P.C.
I am attaching it to you…
Could someone write to me,
how do i change the :
EFI Intel RST RAID Driver - 12.7.0.1936
with the:
EFI Intel RST VMD Driver - 13.2.0.2134
Only by using MMTool.
Without using UBU or UEFiTooL.
The : EFI Intel RST RAID Driver - 12.7.0.1936
It’s about Bios: ASUS X79-DeLuXe 4805.
https://dlcdnets.asus.com/pub/ASUS/mb/LGA2011/X79-Deluxe/X79-DELUXE-ASUS-4805.zip?model=X79-DELUXE 1
Regards.
Dioskouridis.
Sorry to much for reading…
I did not updated the ME FW Image on any of the mod files i did.
This is a user task and can be done manually, by updating the single ME FW image or by rebuild a bios/me_region dumps with the Intel FIT.
If you want to use Lost files, grab them and use UBU to update them, because they’re outdated in some modules/mcodes.
You asked for the IRST 13.2.0.2134 and that’s what i did.
Since we have available .EFI for updating modules we do not use .FFS with MMtool for updates.
FFS is the kind of file (FFS=Complete driver) that MMtool can deal with, not EFI
Still they are available in a thread made by Fernando…i can remember where is it.
Also can be extracted from a bios file
EDIT: And as Fernando already told you there is no Intel® Volume Management Device (Intel® VMD) in those generations and his much more experienced on this subject than me.
I’ve seen UBU sometimes can display “VMD” on some modules versions…but they are iRST
As I already have written to you, it is impossible to do that.
Reason: an Intel RST VMD Driver v13.2.0.2134 doesn’t exist.
Consequence: You can only update the RaidDriver, which is very easy by using the UBU tool.
Hello MeatWar !
Again, thank you for your help.
1.“I did not updated the ME FW Image on any of the mod files i did.”
There is no problem. Changes with a “RepLace” In UEFiTooL … Instantly.
2. “If you want to use Lost files …”
This is what I was thinking… about Bios : X79DLX_ubu_RPL_FFS-Header.rom .
But due to Microsoft Upgrades,
(Every Second Tuesday), when I answered you, I was on another Disk,
with The other O.S. … No Python for UBU (even now I’m on disk No Python)
. . . . . .
Irrelevant :
I always have a Second O.S. in P.C. ,
with an exact same O.S. , with the First O.S. , For security reasons.
It has saved me countless times, because I immediately find all the Files from the Disk,
which rarely happens to not start.
Best Regards.
Dioskouridis.
Hello Fernando!
Finally… honestly… I didn’t realize that:
“an Intel RST VMD Driver v13.2.0.2134 doesn’t exist.”
I inconvenienced you and I feel completely stupid.
But, I’m tired and I’m broke.
I would like a favor from you… maybe the frustration that I’ve been banging my head against the wall for so many days will pass faster.
A (Link) Bios (any)
and
A (Link) for a File “RaidDriver.ffs”
Which becomes “RepLace” with MMTooL.
Best Regards.
And a thousand apologies to you and @MeatWar,
because I have troubled you with my foolishness for so many days.
Dioskouridis.
From: pbatard/efifs in GitHub . com (site):
FFS, which stands for: ‘For F@%k’s Sake, IT’S CALLED A MODULE!!’ is a convenient repackaging of the EDK2’s GenSec and GenFfs utilities, with the aim of easing up the generation of what intel/EDK calls FFS’s (whatever that abbreviation means) which are MODULES, that can be integrated into a regular UEFI firmware.
This can be useful if, for instance, you have UEFI driver executables, which you want to make available in your UEFI “BIOS”.
…
… …
Address Size Designation
EFI_FFS_FILE_HEADER:
0x0000 16 Name (EFI_GUID)
0x0010 1 IntegrityCheck.Header (Header Checksum)
0x0011 1 IntegrityCheck.File → set to 0xAA (FFS_FIXED_CHECKSUM) and clear bit 0x40 of Attributes
0x0012 1 FileType → 0x07 = EFI_FV_FILETYPE_DRIVER
0x0013 1 Attributes → 0x00
0x0014 3 Size, including header and all other sections
0x0017 1 State (unused) → 0X00
EFI_COMMON_SECTION_HEADER:
0x0000 3 Size, including this header
0x0003 1 Type → 0x10 (EFI_SECTION_PE32)
0x0004 ####
EFI_COMMON_SECTION_HEADER:
0x0000 3 Size, including this header
0x0003 1 Type → 0x15 (EFI_SECTION_USER_INTERFACE)
0x0004 #### NUL terminated UTF-16 string (eg “FAT\0”)
EFI_COMMON_SECTION_HEADER:
0x0000 3 Size, including this header
0x0003 1 Type → 0x14 (EFI_SECTION_VERSION)
0x0004 #### NUL terminated UTF-16 string (eg “1.0\0”)
… … …
GenSec -o pe32.sec ntfs_x64.efi -S EFI_SECTION_PE32
GenSec -o name.sec -S EFI_SECTION_USER_INTERFACE -n “NTFS”
GenSec -o ver.sec -S EFI_SECTION_VERSION -n “1.0”
GenFfs -d 1 -g “12341234-1234-1234-1234-123412341234” -o ntfs.ffs -i pe32.sec -i name.sec -i ver.sec -t EFI_FV_FILETYPE_DRIVER
… … …
From: pbatard/efifs in GitHub . com (site):
… … …
…
…
…
…
…
Best Regards.
Dioskouridis.
@Dioskouridis
Although your last post is long and contains links to other contributions, I do not really understand what you really are requesting.
@Fernando I believe Dioskouridis has posted the solution to their problem of newer Intel RST .efi modules not fitting in their BIOS (the difference between v12 and v13 is too great)
They used the ‘ffs’ tool on Gtihub to compress the efi module to the Firmware File System (.ffs) file format (using ED2K and Visual Studio 15).
Which difference between v12 and v13 RaidDriver modules is too great?
If it should be a size problem, wouldn’t it be possible to solve it by removing other (not needed/used) DXE drivers?
@Fernando Yes, it is usually possible to remove something not needed for the extra bytes needed.
Dioskouridis was determined to use MMTool with ffs to retain BIOS structure as Asus BIOS can be finicky.
@chinobino
Thanks for the explanation. Now I understood this specific BIOS modding request.
The user wanted to update the in-use Intel RST RaidDriver module to a bigger sized one, but the ASUS BIOS Flash security mechanism should not recognize this modification. The solution was obviously to shrink the bigger sized module to exactly the same size as the original one by a certain compressing rate.
@Dioskouridis
Since your chosen thread title may be misleading for visitors (as happened for me), it would be a good idea to customize the title. Your problem was obviously not the update of the module, but the proper flash of the modded BIOS, whose Intel RaidDriver was natvely bigger sized than the originally present one.
@Dioskouridis @chinobino @MeatWar
Since I got no reaction to my recent post, I have tried to customize the thread title myself.
According to what I understood, the related method is
a) an option for owners of an ASUS mainboard, whose BIOS doesn’t support the USB Flashback, and
b) usable for all kind of EFI BIOS modules.
If I should be wrong or if you should have a better idea, please re-edit the start post.
Thanks for the interesting thread!
Dieter (alias Fenando)
My view of this user request… he clearly wanted ONLY to use AMI MMtool for module manipulation (.FFS) file method, and seems that chinobino also had the same view of this request.
All this is due to the fact that somehow, he had issues using other tools… we don’t really know what else have been manipulated in his mods, that can lead to this issue he had (missing compressed sections)
What is curious here is that so many users used UBU, specially to update their modules on Asus X79 bioses and never reported back similar issue, related to iRST efi driver.
“IRST .ffs driver manipulation Asus X79”…
A happy and warm new year to all.
@MeatWar
Thanks for your statement!
Another mysterious fact is, that the ASUS X79-DELUXE mainboard supports the USB Flashback feature. So there should not be a big problem to get a modded BIOS properly flashed.
I wish you as well a Happy and Healthy New Year!
@Dioskouridis
Since I am an extremely curious person, I wanted to know the real reason for your problems while trying to update the Intel RST EFI RAID module of your X79 Chipset mainboard BIOS. For this purpose I did some tests with the UEFITool.
As first step I downloaded the latest original BIOS 4805 for your ASUS X79-DELUXE mainboard and opened the *.CAP file by using the UEFITool v0.28.0. Then I tried to update the natively present Intel EFI RaidDriver v12.7.0.1936 (wrongly named by the ASUS’s BIOS “SataDriver_12_7_1036”) to the bigger sized Intel RaidDriver v13.2.0.2134.
Problem: Download links to complete *.ffs files with the correct header starting with 43A0B8C4 for X79 chipset BIOSes are currently not offered within the start post of >this< thread.
My test result: It is possible to replace the hex code of the “pure” RaidDriver v12.7.0.1936 (= “body” of the related PE32 image section) by the “pure” Intel EFI RaidDriver v13.2.0.2134 (without header), which I am offering within the start post of the above linked thread, but the correctly updated module will still be shown as being “SataDriver_12_7_1036” (although it contains the complete “pure” hex code of the v13.2.0.2134 module).
Solution: Creation and usage of a complete Intel EFI RaidDriver v13.2.0.2134 as *.ffs file with the specific header for Intel X79 chipset BIOSes. This file can completely replace the originally present SataDriver/RaidDriver module and will not misleadingly show a wrong version number.
Evaluation of my Test Results:
The AMI Aptio MMTool is not the only one, which is able to get a specific Intel EFI RaidDriver updated, but users with an Intel X79 chipset mainboard may need the specific RaidDriver module as complete *.ffs file with the matching header (here: beginning with 43A0B8C4).
Do you agree with me or am I completely wrong regarding the source of your problems?
@Fernando
Hello Fernando. And happy New Year!
I thank you for your interest.
This is what I couldn’t fix:
*"Creation and usage of a complete Intel EFI RaidDriver v13.2.0.2134 as .ffs file with the specific header for Intel X79 chipset BIOSes.
This file can completely replace the originally present SataDriver/RaidDriver module and will not misleadingly show a wrong version number."
But I haven’t dealt with the right one in a while:
“with the specific header”… . (with effect) and I have lost my handwritten notes.
Now I have a chip ready with 13.1.0.2126 … . (and together with AsMedia106x 4.27 [of UBU because : it is a bit smaller than AsMedia] with MMTool). maybe the error (of defrag) will disappear from the Windows events.
._
The “SataDriver_12_7_1036” … . It changes in UEFITool … with export of the UI … I change it with Hex Edit … and then import.
What is your opinion? : Should I also add “RaidOrom.bin” v3.8.0.1029 … to Disk Controller ? .
Best Regards.
Dioskouridis.
@Fernando
Firmware v4.27 for Asm106x, Available on UBU.
I renamed it to *.rom.
I put it (MMTool and insert) in the bios of the ASUS X79-DELUXE.
On PC Boot, It didn’t show the usual message that … found Asm106x … but in Bios it saw the HDD … and in Windows 10 it worked normally.
- -
16-01-2024
With Driver : Standard SATA AHCI Controller , of Windows → Work.
But
With Driver :Asmedia SATA Controller
; Edited 04/12/2013
DriverVer=06/24/2020, 3.3.5.0000
Indeed it was:
" … he clearly wanted ONLY to use AMI MMtool for module manipulation (.FFS) file method, and seems that chinobino also had the same view of this request. "
With MMTooL I can put more than 1
EFi … on … Disk Controller.
X79 Extreme4-M(3.40)ROM.zip (4.8 MB)
Best Regards.
A happy and warm new year to all.
Dioskouridis.
