I have been working to update the Intel Raid and Realtek LAN modules in the latest Gigabyte EP45-DQ6 BIOS. The Intel AHCI module is already at 1.20E, the latest. In addition I have attempted to remove the existing microcode and replace it with s775 Core2 together with s771 Xeon microcode. Since both modules to be replaced were located below the MINIT module I used CBROM198 to first release the existing ICHARAID.BIN and RTEGROM.LOM and then add the new versions back in. A straight replacement would result in two RTEGROM.LOM modules showing up which is why I chose the release and then add option. CBROM195 was used to replace the microcode as CBROM198 would crash. After the modifications I checked to make sure that MINIT stayed at the same offset (0003C000) which it did. Everything looks pretty good to me but I was hoping someone else could have a quick look before I try and flash. BIOSes attached. 13h is the original.
edit: The OROMs used were: - Intel RST 13.5.0.2164 w/TRIM mod - Realtek v2.63 (confirmed DEV_8168)
edit: - Modified BIOS deleted because I’m not sure it would work - new version below…
Why did you insert into your P45 Chipset mainboard BIOS an Intel RAID ROM module, which has been designed by Intel for the latest Chipsets from 8-Series up? According to my knowledge the TRIM modded Intel RAID ROM v11.2.0.1527 would have been the better choice.
This is what the tool CBROM32_198 shows after having opened both BIOS files (left picture: original BIOS, right picture: your modded BIOS):
My comment: 1. The updates of the Intel RAID ROM and Realtek LAN ROM seems to be fine (no wonder, since both original modules have been beyond the sensitive MINIT module). 2. I am unsure regarding the update of the CPU Microcode, because the size of the NCPUCODE.BIN has been reduced from 130 KB to 76 KB.
Currently RAID 1, although if all this is successful I would be looking to add a RAID 0 array and possibly migrate the RAID 1 array into a RAID 5 array.
Only with the (probably incorrect) thought that newer would be better - I have seen other people updating ICH10R board BIOSes with v12.X and v13.X modules. Is the recommendation to use a v11.X module based on stability/compatibility concerns or because of performance?
The original microcode file covered all s775 chips ever made - both P4 and Core based. The new microcode file contains only the s775 Core microcode plus the s771 Xeon microcode - the s775 P4 microcode is no longer present.
My other option was to try and merge the two files (since space does not appear to be an issue in this BIOS) but I have not yet worked out how to do this yet. I promised I’d take the kids for a bike ride but later today I’ll spend some more time reading the "CPU Microcode BIOS modding questions/problems" thread.
edit: I’ve attached a comparison of the microcodes
Yellow indicates the same microcode exists in both Green/Red indicates newer microcode exists in one (green indicates newer) Blue indicates microcode that only exists in one
Updated modules: - Intel v8.0.0.1039 -> v11.2.0.1527 with TRIM mod - Realtek v2.26 -> v2.63
I had to first release the two modules before adding them back to prevent a duplicate, same as my first attempt.
All modifications done below MINIT.
Original microcode was updated to latest where available, and s771 Core based Xeon microcode added (no P4 based microcode).
The steps I followed to edit the microcode: - create an empty NCPUCODE.BIN file - CBROM195 <BIOS.ROM> /nc_cpucode NCPUCODE.BIN - use Intel Microcode List v0.4a to find individual microcode offsets within NCPUCODE.BIN - download latest microcode package from Intel - extract individual microcode from Intel download using Intel MicroDecode - edit the microcode in NCPUCODE.BIN using a hex editor - use Intel Microcode List v0.4a to make sure everything looks good within NCPUCODE.BIN - mark NCPUCODE.BIN as read only - CBROM195 <BIOS.ROM> /nc_cpucode NCPUCODE.BIN - check final result using Intel Microcode List v0.4a on <BIOS.ROM>
Since I have never tried to update the CPU Microcode of a non-UEFI BIOS, I cannot give you any comment regarding this point. The update of the Intel RAID ROM and Intel LAN ROM should work (provided, that the BIOS is able to load a >100 KB sized Intel RAID ROM module).
Wondering how this BIOS of yours went, any problems? I and two of my friends all have this motherboard, almost upgraded to the brim, but we lacked trim and >2TB. Oh and no optical driver support for the JMicron ports.
Did you manage to get those going? It is stable? I’m super happy finding out that you did a modified bios for this board.
I have this motherboard and I can say from recent (well finally figured it out) experience is that the F13 branch of BIOS breaks the S3 sleep (especially in windows and other DSDT based OS’s I have tried) and the F12 version runs ok with sleep. I flashed a F13h version and the same sleep issues I experienced in F13d were still there, but F12 didn’t have them (not waking correctly from sleep, infinite reboots, etc…) The F12 build on Gigabytes website even states that F12 "Fixed Vista S3 resume sometimes failed" and it does for me, Windows 10 resumes with no issues and when I flash F13*, I get constant sleep / S3 issues with it…
For this I would say the perfect BIOS in my opinion would be all of the above additions, added to the F12 BIOS !!!
Ok, I was going to attempt to do this myself as I do not think it is going to get touched again but am doubting myself and looking for some ideas. As I think I mentioned before I am on some pretty rough cycles of Chemo now and “not all there” but I hope it doesn’t get in my way.
I was wanting to mod the F12 BIOS as it doesn’t have the sleep issues that I am encountering consistently on the F13* builds. I am fine with the microcode in the device as it supports my current Q6600 and my soon to be E5450 Xeon, so I am not touching that. Where I am lost is the AHCI portion, the F12 only has 1.07 and the F13 has 1.20, but from what it sounds like it is the ICHAACHI.BIN file I will need to update to get it to 1.20E (right?) but you guys have mentioned things being above or below the sensitive MINIT module, well this file happens to be above it. What does this mean in my situation? Is it possible and what precautions should I take to not tamper with it? Am I out of luck trying to getting BIOS F12 modded with latest drivers?
-updated, this got me thinking… More than likely the S3 fixes for resume were done via DSDT (ACPI) - I think the F13 version of the ACPITBL.BIN is actually older than the version that is in F12 that is stated to fix S3 resume issues,do you guys think replacing the ACPITBL.BIN file in the F13* version here with the F12 one would fix those resume issues I was having? Should the tables (ACPITBL.BIN) them-self cause any crashes if I replace it alone and it is an older version from F12?
Ok, could someone please update the 13h version 2 file / BIOS in this thread post # 5 (Please make sure it is the second one) to contain this file, the old ACPITBL.BIN from version F12 and keep that file in the second position? I am having a hell of a time doing this… Thank you for the time, it would be much appreciated!!
For what it is worth (Again I have no idea if anyone even watches this thread anymore but it doesn’t seem like it!) I think I may have figured out what is causing the F13 versions to not handle sleep correctly over the F12 version. I compared the two versions and found a few differences but the one that stood out most was in the _WAK method. The F12 had a “Return (Package (0x02)” at the end and the F13 versions didn’t.
Modifying modules above the memory initialisation module is tricky, because the memory initialisation module must remain at the same offset within the BIOS file.
How do the compressed sizes of the ACPI Table modules compare between F12 and F13?
Many thanks to Fernando and JCLW Bios upgraded to a ep45dq6.13h.v2 file. Problem> 2TB solve. But the menu CTRL-I there is no option raid 5. The only option Raid 0. In the Windows and iRST 15.2.0.1020 seen correctly. I decided to delete volume and create a new volume area. the program had all the options: Raid 0,1,5,10. I chose the option: Raid 5 and create normal. but not allowed to create name volume. and not allowed to change name. Is it normal and stable you will?
Is it normal and stable you will is ok? Reboot and in the "Ctrl-I" it appears normal. On "S3 sleep" with Windows 7 x86 I had no problem, but x64 does not sleep. regardless of BIOS f13d old and new modified 13h.v2
@peshocom : Welcome at Win-RAID Forum! Here are my comments:
It was a big mistake to update the Intel RAID ROM to v15.2.0.1020. The latest Intel RAID ROM version, which fully supports your old Intel P45 Chipset system, is v11.2.0.1527.
The best matching Intel RST RAID driver would be v11.2.0.1006 WHQL (Warning: Don’t try to downgrade the Intel RAID driver version, if the RAID array is the system drive!)).
If you want to optimize the performance of your Intel RAID array, you should enable the Write-Back Caching from within the Intel RST Console v11.2.0.1006.
Where can I download The best matching Intel RST RAID driver v11.2.0.1006 WHQL? Not the RAID array is the system drive! Is the data backup drive! My question is: with this version of Raid ROM menu only option Raid 0. I need Raid 5 ? It was once optional ,how created it from the console? Many thanks in advance!
EDIT by Fernando: Unneeded parts of the fully quoted posts removed (to save space)
why those options are not active? if we delete the volume of Raid 5, I will have the option in this configuration to create raid5 again or will I just Raid 0?
EDIT by Fernando: Unneeded parts of the fully quoted post removed (to save space)
Your RAID5 array should still be healthy. Have you uninstalled the previously running version of the Intel Rapid Storage Technology from within the Control Panel ("Add/Remove Programs") before you "downgraded" the RAID driver version? If yes, did you install the complete Intel RST Drivers & Software Set v11.2.0.1006 or just the RAID driver?