Thanks for the info Maximinimaus. I wanted the option to do it - but give then version I might leave it alone. Useful information - I will try playing with updating this module once I have the system going. The board has a backup Bios so I may take a shot
Does anyone know whats the difference between this two modded bioses?: hotfix.chris123nt.com/Asus.Rampage.Formula/Bios.MOD/1002b-R0.zip hotfix.chris123nt.com/Asus.Rampage.Formula/Bios.MOD/1002b-R1.zip And if it's safe to use?.
yes... r0 have jmb 1.08.01 and intel raid 10.1 and r1 have jmb 1.07.27 and intel raid 10.5.1. And yes they are safe to use since im using them for ages.... BTW 10.6. intel rom does not work with out mobo (yet)
HI @ ALL !!! i am new here i hope this is the right 3d to post.. !! Does anyone help me with my RAID problem ?? I have DFI Lanparty DK P35 T2RS with ICH9R 7.5.0.1017 rom . Few days ago i recovered WD 4 RAPTOR: WD740ADFD, and i built raid0 with 4 discs ! It seems works well but after few days i receive many block and errors on the array. WD support sent me a new firmware for my 4 discs "21.07QR5" so i updated without problem. Now i see that ICH9R rom maybe is VERY OLD: 7.5.0.1017 !!! ... so... can i ask you if you can help me modding the latest official DFI Lanparty DK P35 T2RS bios with the latest ICH9R compatible rom (maybe the latest 10 or 8 .. i really dont know) ? here the latest official BIOS from DFI: link 1 (i cannot post link .. PM me) here a modded BIOS that i found googleing... but i dunno if it is safe (maybe check)... : link2 (i cannot post link .. PM me) moreover is there INTEL changelog about fixes on ICH9R roms ? Really, Thank you !! I hope you can help me !!! Thnak thank you ! MJ
I think the latest ROM that works on P35 mobos is 8.5.0.1030. Anything newer causes errors in RAID mode with my abit IP35 Pro.
hum.. ok ! Is there a changelog story about improvements/differences between the older 7.x >> 8.x >> 9.x Intel Ich9r ROM revisions ?
I tried to accomplish the exchange and it works. I edit the mentioned ROM with HxD, open the new ROM with HxD as well, copy the complete contents of the new ROM and do "Paste write" it at the offset in the old big ROM. Reintegration was done with Andy's PhoenixTool. It was very easy.
I asked this already in another thread, but this seems to be the right one. I have to update the RST Option ROM on an MSI board since MSI doesn't do it and I need to make my new 3 TB HDDs work in RAID mode. The board is an MSI P67A-GD65 and here is the newest BIOS for it: download2.msi.com/files/downloads/bos_exe/7681v1D.zip I know that 3TB RAID works with P67 since ASUS did it already: communities.intel.com/message/130008 It seems to be OROM 10.5.0.xxxx Here is a link to the Asus BIOS: bezel.be/P8P67-REV31-ASUS-1850.zip I would prefer the newest OROM version 10.6.0.1091 and by now found it in this thread, but only in .BIN format. Now, after reading what maximinimaus wrote in thread #709 I found that the OROMs are A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_138.ROM in the Asus BIOS and A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_122.ROM in the MSI BIOS, but as in post #709 they seem to contain other PCI-ROMs and differ in offset and size, leading to maximinimaus' recommendation to leave it, but I have to solve it somehow: I just bought 4 3 TB HDDs that I can't use like that. Any help would be appreciated. (Unfortunately I'm not allowed to post links yet so I had to remove the prefix from the links to trick the system )
So, no way to put anything newer then 8.5.0.1030 to my asus p5k-pro? Where to put F5_0000_3.46 in mmtool, i cant find the table for it?
Yes, got the mod done on my MSI Z68A-GD65 after your clue that the Intel Option ROM was in A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_116.ROM module. Did the Hex Edit to 10.6.0.1091 and using Andy's tool integrated the new ROM. BAM it works. I was lucky the version 10.5.0.1034 Option ROM was the exact same size as the new one 10.6.0.1091.
I modified A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_122.ROM to integrate the new Intel Option ROM 10.6.0.1091. The file grew by 35,325 bytes. I successully integrated the modified ROM back into the BIOS using Andy's tool 1.9B4. NOTE: I did a similar upgrade on my Z68A-GD65 board and verified that it works the BIG difference is orginal ROM 10.5.0.1034 and 10.6.0.1091 are of the same size. In your case the orginal ROM and replaced ROM are NOT of the same size. Andy's tool appears to recognize the increased size and fix the checksums and move other modules automatically (take a look at the SLIC.LOG file). NOTE: Backup the existing BIOS to the USB stick using MFlash, and load default settings before you flash the modified bios (does not contain any SLIC). Flashing involves risk including bricking your board and you are flashing at your own risk. Be careful - let us know if this works <Link removed - confirmed not working> - Back to the drawing board.
@m.bezel I strongly advice not to flash the BIOS of post 723. I looked once again in the specific A062CF1F-8473-4AA3-8793-600BC4FFE9A8_1_122.ROM and found following. It seems every contained PCI ROM is prefixed by 10 bytes containing the Id and the length of it. This has to be adjusted for the inserted new OROM. I will look further in this tomorrow, may be I can find a solution.
Bad news: it did not work. Fortunately M-Flash allows to test a BIOS before flashing so I did not brick my board. I have a slightly older BIOS than the current one (1B) so I could test the principle of trying a BIOS file from USB stick. So if I select the unmodified 1D BIOS the board boots with it and reports having booted with it. When I select the modded one the board obviously loads it, but reboots immediately and then stays on without booting. So I think I can say for sure that this mod is not working. Thanks a lot for trying anyway and if someone has another idea how to make it work, I'm still here hoping. Edit: Just read your post, maximinimaus and am glad that you found the reason and that I could try it first. I'm waiting for news and thank you.
OK - I will remove the link, let us wait what maximinimaus finds. Glad you were able to recover without lot of issues.
@m.bezel I think I got it. Please check the attached MSI ROM with your M-Flash tool. You will flash at your own risk! ROM at:hxxp:\\vvv.mediafire.com/?ijyvccd8pw89cwe
Looks like Maximinimaus changed one byte on the header (DC) at offset 1A5D9 which still does not fix it. Looking at my board the 18th byte on the header is also DC. So there is something else we need to adjust. m.bezel have you opened a support ticket with MSI - usually they are pretty good at fixing issues and respond back with a BETA bios fairly quickly.
Actually I did. And it's good to hear that your experience is that I can hope for a fix from them. I usually don't expect much engagement from big companies. But now I have hope .
Yes I set the length of the new ROM. I also made room for the increased OROM and shifted the remainder following the older OROM towards the end. The A062CF1F ROM seems to be very complex and contains many instructions. It's no longer the simple exchange of a new OROM by Intel. Another possibility is that Andy's tool does not work correctly in this situation as it has to move the new longer A062CF1F ROM in the BIOS space and do some adjustments. At the moment, we can only exchange OROMS of equal length.
I see. Thanks again for your effort anyway. Now I'm hoping that MSI will take care of it. And if they don't I'll certainly dump this board, get an Asus and never buy MSI anymore.