1. I talked about rebuilding a RAID1 volume. 2. Did You also measure the time of the rebuilding with the older OROM's and the newer Intel Rapid Storage software? Following is an excerpt from Intel® Rapid Storage Technology OEM Technical Guide For the Intel® Rapid Storage Technology 10.5 Software Package Revision 1.01 3.2 Intel® Rapid Storage Technology Option ROM The Intel® Rapid Storage Technology Option ROM is a standard Plug and Play option ROM that adds the Int13h services and provides a pre-OS user interface for the Intel® Rapid Storage Technology solution. The Int13h services allow a RAID volume to be used as a boot hard drive. They also detect any faults in the RAID volume being managed by the RAID controller. The Int13h services are active until the RAID driver takes over after the operating system is loaded. Another excerpt from an Intel document CS-020657.htm It is okay to upgrade to a newer version of Intel® Rapid Storage Technology (for example, v10.1) if you have an older version of the option ROM (for example, v9.6) installed. The option ROM version does not need to match the version of Intel® RST. Each version of the option ROM supports a specific set of hardware, as shown by the following examples ....
@mynameistpx What tool did you use to insert the ROM? And do you use the drives in RAID mode? I have a Maximus III Formula (P55) MB. I used MMTool 3.26 and every ROM after 10.1.0.1008 failed. I tried 10.5.0.744, 10.5.0.1034, 10.5.1.1070 & 10.6.0.1091. With all of them I could detect the drives, see the Raid 0 matrix, enter the menu (Ctrl + I) but after that the system just hanged. I had to remove the battery be able to reflash a good bios. Also if I did not use the drives in RAID mode it would have worked (i could get the system to boot)
Really? I always thought the OROM did the job before loading the OS. If so, why does it have to be so large?!
I have used both mmtool 3.22 & till recent v3.26, both tools works well. Intel RST 10.1.0.1008, 10.5.0.1034, 10.5.1.1070 & 10.6.0.1091 all work well on EVGA P55 Micro and Asus Maximus III Gene. EVGA P55 Micro is running AHCI mode while the Asus Maximus III Gene is on Raid1 (using latest RST 10.6.0.1002 driver & utility) without problems. I also successfully loaded up and can configure the Intel RAID Utility during the bootup POST (Ctrl+I). What was your failure message?
BTW, I have updated the option-rom of LAN (realtek v2.41) and JMicron (jmb363 v1.07.28) for my Maximus III Gene. I don't know if this makes a difference.
Hi, I updated latest 0701 bios for Asus P6X58D-E with Intel Option ROM to 10.1.0.1008 and Marvell PXE Rom to 6.68.1.3; could someone add latest Marvell 9128 Rom/Firmware, please? I can't get it work... xxx.megaupload.com/?d=62PQW4DP
I do not think it's to large. It's about 120 kb. The corresponding RaidCfg tool by Intel is about 147 kb. RaidCfg is a DOS program that does the same as the OROM does after pressing CTRL I.
Now I run 10.1.0.1008 ROM in BIOS, the 10.6.0.1002 drivers and 2x80GB X25-M in RAID 0 and 2 other HDD with no errors. I have the LAN (realtek) & JMicron disabled. I use a PCIE card Intel Gigabit CT Desktop Adapter as a network card. During the ROMs replacement and BIOS flashing there was no error. The thing that happens is that after Intel Raid Utility gets loaded during POST the system hangs (usually with a black screen) and it does not continue to POST and bootup (the intel raid utility functions normally: I see the drives, the raid 0 matrix, can enter it, exit it ...). I thought that these last ROMs being larger don't get replaced properly by the MMTool 3.26 since the Asus Maximus III Gene is basically the same with the Maximus III Formula. Strange that it does not work at my end.
Anyone figured out a way to update Intel ROMs in a UEFI bios? Using Andy's tool and looking at the DUMP folder is not much help. Looks like the files are compressed. Anyone figured this out?
If you doubt that the option-rom insertion, you can simply extract that option-rom and open with notepad to see if it's really 10.6.0.1091 from the MODDED ROM. BTW, please see my attached picture that I am running option-rom 10.6.0.1091 & driver 10.6.0.1002. It's on RAID1.
Can you tell me a download location for the BIOS and I will take a look! I successfully replaced the Intel ROM in BIOS F.13 of a HP EliteBook 8530w with Andy's tool. This was an EFI/Insyde BIOS.
Why do you want to replace the OROM? The B3 BIOS contains already the OROM V10.5.0.1034. It is contained in module A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_116.ROM at offset 56424 to 74023(hex). The module contains also other PCI ROMs!! I think you can edit the A062CF....ROM with HxD and paste the desired OROM at that offset as the length of both versions of the Intel OROM are the same. But I don't know if the A062CF...ROM is secured with a checksum!! If you succeed in replacing the OROM with the new one, let me know and I will guide you further. Good luck!
I don't now if the BIOS I am trying to update just won't work with this version or if I'm doing something wrong, but it just saves my BIOS file as an empty file when I use this tool. Here is what I am trying to accomplish: I want to extract the newer Intel RST OROM from the ASUS P8H67-M EVO BIOS (I believe it has OROM version 10.5.x) and insert it into the BIOS for my P8H67-M LX board. These are very similar boards, both based on the H67 chipset, expect that the EVO is ASUS's flagship board for this line, and it gets all the recent updates. If anyone could help me I'd be happy to test out the results. Here are the BIOS download links: ASUS P8H67-M EVO (extract OROM from this one): hxxp://dlcdnet.asus.com/pub/ASUS/mb/LGA1155/P8H67-M_EVO/P8H67-M-EVO-ASUS-1850.zip ASUS P8H67-M LX (replace OROM with one extracted from above BIOS): hxxp://dlcdnet.asus.com/pub/ASUS/mb/LGA1155/P8H67-M_LX/P8H67-M-LX-ASUS-0802.zip
Both BIOS are EFI/Insyde so Andy's Tool should work. And it does. 1850 contains module A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_127.ROM which contains OROM V10.5.0.1034 at offset 19BFC(hex). 0802 contains module A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_118.ROM which contains OROM V10.1.0.1008 at offset 296A6(hex). Both modules contain other PCI-ROMs. The length of the 2 versions of the Intel Raid ROMs differ, so they are not easily exchangeable via HxD. Also the offsets differ. My advice is, stay with the BIOS 0802 otherwise there is a great chance to brick it with any modification of it. My opinion is, the performance of the Raid array depends primarily on the driver and not on the OROM. Look at my post 692 in this thread.
It's not so much about preformance with me as reliability. There is somehting wrong on my brand new board (I'll probably RMA it), in that the OROM screws up on every cold boot; the initial info screen loses the first drive in the RAID array (always the first port no matter which way I choose to build it or reconnect it after the fact), but when I Ctrl-I into the configuration menu, it's back at the bottom of the list (out of the correct order, i.e. 2,3,4,1). Ony any subsequent warm boot after accessing the menu, the drive appears as normal on both screens, btu a new cold boot will reintroduce the problem. The biggest problem is that it will trigger a rebuild on any volume with redundancy. On a RAID 0 array, it shows "Failed" status until accessing the configuration menu, where it returns to normal with no data loss. I was hoping that maybe this was some sort of bug in the BIOS and that an upgrade would maybe fix it. Oh well. Thanks for your help, I'm much too inexperienced to attempt hex editing.
Thank you very much! I already added Intel Option ROM 10.1.0.1008 (latest working for P6X58D-E) and Marvell PXE Rom 6.68.1.3, I missed only Marvell 9128... Will EZ Flash 3.46 work fine? Stock is 3.44, I wouldn't like to brick EZ Flash, it's very practice...