BIOS-Modding: How to update PCI ROM modules of an AMI/Phoenix/Award BIOS

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

1

Friday, January 20th 2012, 10:21pm

@ all visitors of this thread:

When I started this English language thread within the German Win-Lite Forum, I didn't expect, that it would get much more visitors than the German thread with the similar topic.
Additional problem of 2 separate threads with the same topic, but for users with a different language: Some users mixed the threads and posted in German within the English thread and others did it vice versa.
That is why I decided to start a brandnew and completly English language Forum named "Fernando's Win-RAID Forum" with the main topics "AHCI/RAID drivers" and "BIOS Modding". You can find this new Forum inclusive all my BIOS modding guides and my collection of the actual AHCI/RAID ROM modules >here<.

Since I will not support this thread anymore in the future, it would be a good idea to write your questions, answers and statements into the freshly created thread at my "Win-RAID Forum".
Nevertheless this thread will stay accessible for you. So you will still have the opportunity to read all posts, which are within this or another thread of German Win-Lite.
I would be very pleased, if you decide to visit and to register at "Fernando's Win-RAID Forum".

Kind regards
Dieter (alias Fernando)

____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

@ all experienced and courageous users, who want to update a PCI ROM module of their mainboard BIOS:

Preliminary notes:

Since I have some experience regarding the extraction and replacement of PCI ROM modules, which are part of the mainboard BIOS, I decided to create and to publish this step-by-step guide about how to do it.
Although these detailed instructions are mainly written for users, who want to update the Intel RAID ROM module of their mainboard BIOS, they basically can be used for the extraction and replacement of any other PCI ROM module too.
Users with a Phoenix/Award BIOS system will find a similar guide within the second post of this thread.

Here is the guide for users with an AMI BIOS system:

BIOS Modding:
I. How to update PCI ROM modules of an AMI BIOS

Important informations:
Warning: Modding a BIOS file by updating the inserted PCI ROM module is neither very difficult nor risky, but it is extremely dangerous, if you are going to flash a modded BIOS into the BIOS chip of a mainboard. In the worst case you may not be able to use the computer anymore until you will get a new and working BIOS chip from the manufacturer of your mainboard.
This is why I recommend to flash a modded BIOS only for experienced users, who know about the risks and do all necessary preparations for the worst case (inclusive a complete backup of their data).
There is no warranty regarding the safety of my guide and the linked BIOS and PCI ROM files. Everything you are doing will be at your own risk.
AMI BIOS files do not contain any separate AHCI ROM module. The SATA AHCI Controller of the mainboard will be supported by the RAID ROM module. That is the reason why users with an AHCI (non-RAID) system may benefit from an update of the RAID ROM version.
The PCI ROM modules are within the mainboard BIOS file and only visible by opening the BIOS file with a special tool like MMTool. Nevertheless it is possible to extract any PCI ROM module and to replaced it by another version, because the entire mainboard BIOS file has a modular structure.
Although the BIOS files are developed and published by the mainboard manufacturer, the inserted PCI ROM modules were made by the vendor of the related on-board Controller chips. Each PCI ROM module version, which has been delivered from the Controller chip vendor to the mainboard manufacturers, is identical and not depended on the BIOS structure (AMI/Phoenix/Award) the mainboard manufacturer is using. As a consequence each extracted PCI ROM file can be inserted into each mainboard BIOS, which already contains the same sort of PCI ROM module.
Basically the extraction and the replacement procedure of all PCI ROM modules is quite similar. That is why this guide is usable for users too, who want to modify any other PCI ROM module from any other vendor.

A. Preparations
(valid for UEFI and non-UEFI AMI BIOS files)

This is what you should prepare, if you want to extract a PCI ROM module from an AMI mainboard BIOS or to replace a PCI ROM module from within an AMI mainboard BIOS:

Download the following files and tools:
1. the actual motherboard BIOS for your motherboard or system
  (get it from the manufacturer)
2. the appropriate AMI BIOS processing tool named MMTool
  Depending on the sort of the AMI BIOS you are going to process (non-UEFI or UEFI) you will need
  - either the standard (non-UEFI) AMI BIOS tool MMTool v3.26 (runs with all actual 32/64bit Windows Operating Systems)
    This tool can be downloaded from here:
    - >MM-Tool v3.26<
  - or the special AMI Aptio EFI MMTool v4.50.0.23 (runs with all actual 32/64bit Windows Operating Systems)
    You can get this tool from here:
    - >Aptio UEFI MMTool v4.50.0.23<
  If you are not sure, which tool you will need, you should download them both.
3. the PCI ROM module file you want to insert into your BIOS
  - either as already extracted uncompressed PCI ROM file
  - or as complete AMI BIOS file, where you want to get the desired PCI ROM module extracted from
  Note: You can find download links to a lot of actual and already extracted AHCI/RAID ROM modules from different chipset manufacturers within the start post of >this< thread.
4. optional: any Hex Editor like HxD (just to verify the Intel RAID ROM version)
  >Here< is the link to the tool HxD
Create a special folder within any partition of your hdd/SSD (example: C:\test) and copy all previously downloaded and unzipped files into it.
Just for the emergency case you should leave a copy of your original mainboard BIOS file somewhere else outside the system (example: USB stick)
If the mainboard BIOS file does not have the suffix ".ROM" rename the suffix to ".ROM". This is necessary, because the MMTool prefers to open ".ROM" files.

Additional remarks:

AHCI and RAID systems generally will work at its best, when the in-use RAID ROM module (="firmware" of the AHCI/RAID Controller) and the in-use AHCI/RAID drivers belong to the same generation (for Intel: MSM/RST/RSTe) and - if possible - to the same version series (e.g. Intel MSM v8.9 or Intel RST v10.1).
Unfortunately there are some technical limitations, because the actual PCI ROM modules are not fully backwards compatible. Only the owners of a brandnew mainboard or pc can be sure, that the newest PCI ROM version definitively will work. As a consequence users with an older hardware configuration have to find out themselves (or by a Google search) the last PCI ROM version, which is suitable for their mainboard/system.
Users, who have flashed a BIOS with an uncompatible Intel RAID ROM version, probably will not be able to run and/or to use the Intel RAID ROM Utility (by hitting CTRL+I), but usually this problem can be solved by reflashing the original BIOS.

B. Processing of a normal (non-UEFI) AMI BIOS file

1. Opening a non-UEFI AMI BIOS file
This is what you should do:

Run the Windows Explorer and open the previously created BIOS processing folder (e.g. C:\test).
Right click onto the MMTOOL3.26.EXE and choose "Run as Administrator".
Hit the "Load ROM" button, browse to the AMI BIOS file, which is within the processing folder (e.g. C:\test). and open it. If the MMTool doesn't find the BIOS file, you probably forgot to rename the suffix of it to ".ROM".
After having successfully opened the AMI mainboard BIOS file, the GUI of the MMTool will show you the content of the BIOS file within a great window on the buttom of the MMTool GUI:

If the MMTool v3.26 should not be able to open the AMI BIOS file, it probably is not an AMI standard BIOS, but an AMI UEFI BIOS file. In this case you have to use the special AMI Aptio UEFI MMTool v4.50.0.23 (see the next chapter).

2. Finding the Intel RAID ROM Module within a non-UEFI AMI BIOS file
Here are some advices to make it easier for you:

All PCI ROM Modules of the mainboard BIOS are named "PCI Option ROM" and can easily be found by scrolling down within the great MMTool content window.
To find out the sort and function of the different listed "PCI Option ROM" modules, you have to highlight the related line. After having done that, you will see the needed details within the "For Adapter ROM only" section of the MMTool GUI. The vendor of the PCI ROM module is shown with the 4 characters (digits or letters) of his unique VendorID (VEN_xxxx) and the related device with the 4 characters (digits or letters) of its unique DeviceID (DEV_xxxx):

Examples:
The chipset manufacturer with the VendorID VEN_8086 is the Company Intel.
So if you are searching for any Intel PCI ROM module, you have to focus on all "PCI Option ROM" lines, where the "8086" is shown as VendorID.
If you see more than 1 "PCI Option ROM" with the VendorID "8086" (= VEN_8086), you should check the associated Device ID:
- The Device ID with the digits "2822" (= DEV_2822) is the "Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller", which is the on-board Intel RAID Controller of mainboards with an ICH8R, ICH9R, ICH10R, 5-Series and 6-series Southbridge.
  The Device ID with the digits "282a" (= DEV_282a) is the "Intel(R) Mobile Express Chipset SATA RAID Controller" and the on-board Intel RAID Controller of mobile (laptop) mainboards with a Southbridge from ICH8M up.
  Important: Both Intel Devices DEV_2822 and DEV_282a need and are using exactly the same Intel RAID ROM module. That is why some mainboard manufacturers are lazy while building the BIOS file and give both types of mainboards (Desktop and Mobile) the same DeviceID (e.g. "282a"). So don't worry about it, if you are checking a Desktop mainboard BIOS, but see "8086,282a" shown by the MMTool.
  By the way: The shown digits of the Vendor and Device IDs don't have any influence on the function of the BIOS or the ROM modules.
- The DeviceID "2826" (= DEV_2826) is the "Intel(R) C600 Series Chipset SATA RAID Controller", which is the on-board Intel RAID Controller of mainboards with an Intel X79 chipset.
So if you want to extract or replace an Intel RAID ROM module, which is compatible with Intel's ICH8R/ICH9R/ICH10R/5-Series/6-Series Chipsets, you have to look for a "PCI Option ROM" with the shown VendorID "8086" and DeviceID "2822", whereas users with an Intel X79 chipset mainboard should search for the "PCI Option ROM" with the Vendor ID "8086" and the DeviceID "2826".
You can easily find out the vendor and device names of shown VendorID's and DeviceID's with other characters by doing a Google search. Just edit the VendorID as "VEN_xxxx" and the DeviceID as "DEV_xxxx" - each ID with the shown characters.

3. Extraction of an Intel RAID ROM module from a non-UEFI AMI BIOS file
Generally notes:

The extraction of a PCI ROM module doesn't effect the mainboard BIOS. It will stay untouched by the extraction.
It is impossible to verify the version of the PCI ROM module as long as it is part of the BIOS file. So you have to extract it, if you want to make sure, that it is the desired version, which you want to flash into your own mainboard later.

This is the procedure:

Start the MMTool v3.26, hit the "Load ROM" button and load the AMI BIOS file, which contains the desired PCI RAID ROM version.
Search for the "PCI Option ROM", which is the desired Intel RAID ROM Module, and highlight the related line within the MMTool window.
Hit the tab "Extract", go to the "Module file" box and edit a name for the module file you want to extract. PCI ROM mudule files usually have the suffix ".BIN" (e.g. RAID_ROM.BIN).
Make sure, that the default option "Extract Module in uncompressed form" is enabled.
The GUI of the MMTool should look like tis:
Now hit the "Extract" button.
You will find the extracted file (named RAID_ROM.BIN or similar) within the processing folder (C:/test).
As last step you should verify the sort and the version of the extracted Intel RAID ROM file.
Just open it with a Hex Editor and you will find on top of the right side a readable text with the sort and the version of the PCI ROM module (example: "Intel(R) RAID for SATA - v10.6.0.1091"):

This means, that you have extracted the Intel RAID ROM v10.6.0.1091.

4. Replacement of an Intel RAID ROM module from within a non-UEFI AMI BIOS file
This is what you should do:

Run the MMTool v3.26, hit the "Load ROM" button and and navigate to the AMI BIOS file you want to modify (it should be within C:\test).
Search for the "PCI Option ROM" you want to replace and highlight the related line.
Hit the "Replace" tab.
Now you can see the details (ModuleID, VendorID and DeviceID) of the "PCI Option ROM" you are going to replace by another version.
After having made sure, that the shown "PCI Option ROM" details are the correct ones, hit the "Browse" button and navigate to the Intel RAID ROM file you want to get into the AMI mainboard BIOS (it should be within C:\test and have the suffix ".BIN").
Open the .BIN file by enabling it and hitting the "Open" button or by double click onto the file.
Now the MMTool GUI should like like this:
If everything is ok, hit the "Replace" button. This will execute the replacement of the selected "PCI Option ROM" module.
It is possible, that you will see some slightly changes regarding the size of the modules, which are listed within the MMTool GUI window. This happens, when the size of the inserted module is different from the replaced one.
In my test scenario I got some changes you see here:

Don't worry about these changes. The MMTool is able to compress the modules dynamicly (within a certain bandwidth) with the result, that all modules will be completely inserted without changing the size of the entire mainboard BIOS file.
Attention:
Old AMI BIOS files are only small sized and it may happen, that the compression potential is not able to replace a small sized PCI ROM Module by a much bigger one. In this case you will get an adequate message.
Tip:
In some cases you can solve the space problem by deleting a module, which is not that important for the use of the computer, for example the "OEM Logo".
Just hit the "Delete" tab, highlight the line with the module you want to delete (example: "OEM Logo") hat hit the "Delete" button. After having done that you can try the replacement of the PCI ROM module again.
As last step the modified BIOS file has to be saved.
Hit the "Save ROM as ..." , create a useful name for the modded BIOS file (example: P8Z68-V-ASUS-0801_mod.ROM) and then save it.
You will find the modded BIOS file within your processing folder (C:\test). Due to the dynamic compression done by the MMToool it should have exactly the same size as the original BIOS.

C. Processing of an AMI UEFI BIOS file

1. Opening an AMI UEFI BIOS file
The UEFI type AMI BIOS files can easily be identified by their big size of more than 8 MB.
This is the way to open them:

Run the AMI Aptio MMTool.exe as Administrator
Hit the "Load Image" button, browse to the AMI UEFI BIOS file you want to open (named xxxx.ROM) and double click onto it.
Now the Aptio MMTool GUI will look like this:

If the Aptio MMTool is not able to open the AMI BIOS file, it is not an AMI UEFI BIOS. In this case you have to use the MMTool v3.26 and to follow the instructions of Chapter B.

2. Extraction of the Intel RAID ROM module from an AMI UEFI BIOS file
Generally notes:

The extraction of a PCI ROM module doesn't effect the mainboard BIOS. It will stay untouched by the extraction.
It is impossible to verify the version of the PCI ROM module as long as it is part of the BIOS file. So you have to extract it, if you want to make sure, that it is the desired version, which you want to flash into your own mainboard later.
Contrary to the non-UEFI AMI BIOS the important PCI ROM modules of the AMI UEFI BIOS files are hidden and cannot be seen by opening the BIOS file. The shown modules named "AHCI" or "SBAHCI" are just copies of the original RAID ROM module, which is hidden.

This is the procedure:

Run the Aptio MMTool and open the mainboard BIOS file (see above).
Scroll down within the Aptio MMTool GUI window and search for the FileName "CSMCORE" with the GUID beginning with "A062CF1F-8473-" and highlight the related line:
Hit the "Extract" tab and make sure, that the line with the FileName "CSMCORE" is still highlighted.
Go to the "For Option ROM only" section, enable "Link Present" and scroll down to the correct VendorID (8086 = Intel) and DeviceID of your on-board RAID Controller.
Examples:
- DEV_2822 = "Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller"
- DEV_282a = "Intel(R) Mobile ExpressChipset SATA RAID Controller"
  Important: Both Intel Devices DEV_2822 and DEV_282a need and are using exactly the same Intel RAID ROM module. That is why some mainboard manufacturers are lazy while building the BIOS file and give both types of mainboards (Desktop and Mobile) the same DeviceID (e.g. "282a"). So don't worry about it, if you are checking a Desktop mainboard BIOS, but see "8086,282a" shown by the AMI Aptio MMTool.
By the way: The shown digits of the Vendor and Device IDs don't have any influence on the function of the BIOS or the ROM modules.
If you do not find the DeviceID of your on-board RAID Controller, you may not be able to use the extracted Intel RAID ROM with your system.
Hit the "Browse" button and search for the folder, where you want to store the extracted RAID ROM BIOS file, choose any file name with the suffix .BIN (example: RAID_ROM.BIN) and hit "Store".
Here is the related screenshot:
Hit the "Extract" button of the Aptio MMTool.
Now you will find the extracted Intel RAID ROM module as .BIN file within your test folder (C:\Test).
If you want to know the version of the extracted Intel RAID ROM module, you should open it with a Hex Editor. You will see the version on top of the right side (see the picture within the chapter C 3.)

3. Replacement of the Intel RAID ROM module from within an AMI UEFI mainboard BIOS
This is what to do:

Open the BIOS file and highlight the line containing the hidden PCI ROM module as written within chapter 2.
Hit the "Replace" tab of the Aptio MMTool and browse to the Intel RAID OROM file (named xxxx.BIN) you want to get flashed and open it.
Go to the "For Option ROM only" section, enable "Link Present" and scroll down to the correct VendorID (8086 = Intel) and DeviceID (Example: 2822 = "Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller") of your on-board RAID Controller.
This is what you should see, if your system has an Intel ICH8R, ICH9R, ICH10R, 5-Series or 6-Series chipset:

Note:
The "For Option ROM only" section only shows the VendorID and DeviceID of the RAID ROM Modul, which has been inserted by the manufacturer of the original AMI UEFI mainboard BIOS file. So you will get no information regarding the VendorID and DeviceID of the RAID ROM file you are going to insert now by doing the replacement.
Hit the "Replace" button and then either the "Save Image" or - if you want to rename the BIOS file - the "Save Image as ..." button.
Wait some seconds, before you close the MMTool.
After having done all that correctly, you will find the modified BIOS within the folder where the original BIOS file was (C:\Test) or within the folder you had chosen while saving the modified one. The "modded" BIOS file should have exactly the same size as the original one, but a different date.
If you should get an "Error in Replacing File" message while trying to replace a RAID ROM module, the mainboard manufacturer may have inserted the related special RAID ROM module twice (by mistake), but with different DeviceID's.
Solution: Remove one of the identical PCI ROM modules (example: 8086,2822) by using the MMTool "Delete" tab and then retry the replacement of the other one (example: 8086,282a).

D. Flashing the modded BIOS into the mainboard BIOS chip
(valid for UEFI and non-UEFI AMI BIOS files)

It is strongly recommended to follow the following advices:

Before you are going to flash the new BIOS, you should make a complete backup of your entire system and boot partitions or at least of all important data. After having done that, enter the BIOS and list all your special settings. Before you leave the BIOS, choose and save the DEFAULT settings.
Since the BIOS file name usually is layed down by the mainboard manufacturer within the BIOS itself, the "modded" BIOS file should not be renamed unless the new name is "in the line" with BIOS files, which were previously released by the manufacturer.
Users with an ASUS mainboard, who get a "Security Verification" warning while trying to flash a modified BIOS, should redo it by using the "USB BIOS Flashback" method (for details look into the mainboard manual, not all ASUS mainboards do support it). Important: The BIOS has to be renamed a special way according to the ASUS PDF files, if you use the ASUS "USB BIOS Flashback" method!
Users with an ASUS P8xxx mainboard, which doesn't support the "USB BIOS Flashback" feature, may get the modified BIOS successfully flashed by following >this< guide layed down by CodeRush at [H]ard|Forum (thanks to Maikl for the tip).
After having flashed the new BIOS, you have to redo your previous BIOS settings.
Safest way (found >here<):
After flash is complete, shut down fully and switch off PSU, wait one minute and clear CMOS. Then turn on, boot to BIOS, load optimized, set the SATA Controller to the appropriate mode (AHCI/RAID) and save/apply/reboot back to the BIOS. Once in the BIOS again recover the previous boot settings (boot device and HDD boot order). If you have updated the Marvell 91xx AHCI/RAID ROM module, set the Marvell Firmware mode to "Force", then save/apply/reboot and let it load through to windows, before that happens Marvell Firmware will update and board will reboot.
Before you restart with your usual PC work, you should verify the full function of the updated PCI ROM module. If you have inserted a new RAID ROM version into the BIOS, you have to make sure, that the "RAID" mode of the on-board SATA Controller is enabled, and then you should run the RAID Configuration Utility by hitting CTRL+I, F10 or similar (look into your mainboard manual). Everything will be fine, if you can enter and use the RAID Configuration Utility without any problem (Don't modify anything, if you don't want it to be changed!).
Advice for users with a non-RAID system:
Users, who are running their SATA Controllers in AHCI or IDE mode, should check the function of the freshly updated RAID ROM module the same way. After having temporarily enabled the "RAID" mode of the on-board SATA Controller they should run the RAID Configuration Utility and look, if everything seems to be fine (but don't create a RAID array!). Then they can close the Utility and reset the SATA Controller to the usual setting (AHCI/IDE mode). The data of their AHCI/IDE system will not be altered or destroyed by this procedure.

Any feedback is much appreciated. Most important is a short report about the success or failure of flashing the "modded" BIOS into the BIOS chip of your mainboard. Don't forget to mention the vendor and the name of your mainboard and the sort and version of the flashed PCI ROM module. You can write in english, french or german language.
If this guide was a help for you and you want to say "Thanks", you can hit the "Danke" button on the buttom of this post.

Good luck!
Fernando

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

This post has been edited 39 times, last edit by "Fernando" (May 10th 2013, 9:32pm)

10 registered users and 29 guests thanked already.

Users who thanked for this post:

Helmi, Sir Gibson, newererst, KevinNash, adb, splicegirl, kknight, VeixES, Dozz, odiebugs

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

2

Monday, January 30th 2012, 9:36pm

@ all visitors of this thread:

When I started this English language thread within the German Win-Lite Forum, I didn't expect, that it would get much more visitors than the German thread with the similar topic.
Additional problem of 2 separate threads with the same topic, but for users with a different language: Some users mixed the threads and posted in German within the English thread and others did it vice versa.
That is why I decided to start a brandnew and completly English language Forum named "Fernando's Win-RAID Forum" with the main topics "AHCI/RAID drivers" and "BIOS Modding". You can find this new Forum inclusive all my BIOS modding guides and my collection of the actual AHCI/RAID ROM modules >here<.

Since I will not support this thread anymore in the future, it would be a good idea to write your questions, answers and statements into the freshly created thread at my "Win-RAID Forum".
Nevertheless this thread will stay accessible for you. So you will still have the opportunity to read all posts, which are within this or another thread of German Win-Lite.
I would be very pleased, if you decide to visit and to register at "Fernando's Win-RAID Forum".

Kind regards
Dieter (alias Fernando)

____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

BIOS Modding:
II. How to update PCI ROM modules of a Phoenix/Award BIOS

Important informations:
Warning: Modding a BIOS file by updating the inserted PCI ROM module is neither very difficult nor risky, but it is extremely dangerous, if you are going to flash a modded BIOS into the BIOS chip of a mainboard. In the worst case you may not be able to use the computer anymore until you will get a new and working BIOS chip from the manufacturer of your mainboard.
This is why I recommend to flash a modded BIOS only for experienced users, who know about the risks and do all necessary preparations for the worst case (inclusive a complete backup of their data).
There is no warranty regarding the safety of my guide and the linked BIOS and PCI ROM files. Everything you are doing will be at your own risk.
Although the Phoenix/Award BIOD files usually contain a separate AHCI ROM module, the SATA AHCI Controller of the mainboard may be supported by the RAID ROM module too. That is the reason why users with an AHCI (non-RAID) system may benefit from an update of the RAID ROM version.
The PCI ROM modules are within the mainboard BIOS file and only visible by opening the BIOS file with a special tool like CBROM. Nevertheless it is possible to extract any PCI ROM module and to replaced it by another version, because the entire mainboard BIOS file has a modular structure.
Although the BIOS files are developed and published by the mainboard manufacturer, the inserted PCI ROM modules were made by the vendor of the related on-board Controller chips. Each PCI ROM module version, which has been delivered from the Controller chip vendor to the mainboard manufacturers, is identical and not depended on the BIOS structure (AMI/Phoenix/Award) the mainboard manufacturer is using. As a consequence each extracted PCI ROM file can be inserted into each mainboard BIOS, which already contains the same sort of PCI ROM module.
Basically the extraction and the replacement procedure of all PCI ROM modules is quite similar. That is why this guide is usable for users too, who want to modify any other PCI ROM module from any other vendor.

A. Preparations

This is what you should prepare, if you want to extract a PCI ROM module from a Phoenix/Award mainboard BIOS or to replace a PCI ROM module from within a Phoenix/Award mainboard BIOS:

Download the following files:
1. the actual mainboard BIOS for your system
  (from the web sites of the manufacturer)
2. the appropriate Phoenix/Award BIOS processing tool named CBROM
  This is the CBROM version I recommand to download and to use:
  - >CBROM32_198.EXE< (renamed by me to "CBROM.EXE" to make it easier for you, works in the DOS box of all actual Windows Operating Systems, even within a 64bit environment)
  If this CBROM version should not handle your special Phoenix/Award BIOS file correctly, you should download and try another CBROM version you get >here<. Attention: None of these CBROM versions will work in a 64bit environment, some of them need to be run in real DOS mode.
3. the PCI ROM module file you want to insert into your BIOS
  - either as already extracted uncompressed PCI ROM file
  - or as complete Phoenix/Award BIOS file, where you want to get the desired PCI ROM module extracted from
  Note: You can find download links to a lot of actual and already extracted AHCI/RAID ROM versions from different chipset manufacturers within the start post of >this< thread.
4. optional: any Hex Editor like HxD (just to verify the Intel RAID ROM version)
  >Here< is the link to the tool HxD
Create a special folder within any partition of your hdd/SSD (example: C:\test) and copy all previously downloaded and unzipped files into it.
Just for the emergency case you should leave a copy of your original mainboard BIOS file somewhere else outside the system (example: USB stick).

Additional remarks:

AHCI and RAID systems generally will work at its best, when the in-use RAID ROM module (="firmware" of the AHCI/RAID Controller) and the in-use AHCI/RAID drivers belong to the same generation (for Intel: MSM/RST/RSTe) and - if possible - to the same version series (e.g. Intel MSM v8.9 or Intel RST v10.1).
Unfortunately there are some technical limitations, because the actual PCI ROM modules are not fully backwards compatible. Only the owners of a brandnew mainboard or pc can be sure, that the newest PCI ROM version definitively will work. As a consequence users with an older hardware configuration have to find out themselves (or by a Google search) the last PCI ROM version, which is suitable for their mainboard/system.
Users, who have flashed a BIOS with an uncompatible Intel RAID ROM version, probably will not be able to run and/or to use the Intel RAID ROM Utility (by hitting CTRL+I), but usually this problem can be solved by reflashing the original BIOS.

B. Processing of a Phoenix/Award BIOS

Opening a Phoenix/Award BIOS
This is what you should do:

Open the Command Prompt (CMD.EXE) as administrator and navigate by using the special commands like "CD" into the processing folder you have created (e.g. C:\test).
Execute the following command (without the angular brackets, but with the complete name of the mainboard BIOS file, using capital or small letters doesn't matter):
Source code

1

CBROM.EXE <name of the mainboard BIOS file> /D
If the BIOS file and the CBROM tool are matching, you now will see the content of the mainboard BIOS and even the names of the currently inserted RAID ROM module (e.g. ICHARAID.BIN). By the way: If you want to replace it by another RAID ROM version, you should customize the name of your prepared RAID ROM file. Only PCI ROM files with the exact similar name will be completely replaced.
Example:
This is a screenshot after having opened the mainboard BIOS named X58AUD3R.FH of the GIGABYTE mainboard GA-X58A-UD3R by using the tool CBROM:

In this case the Intel AHCI ROM module is listed within line 14 (recognizable by the name on the right side), has the internal PCI ROM module letter "A", an uncompressed size of 16,00 KB, a compressed size of 10,82 KB and is named ICHAAHCI.BIN.
The Intel RAID ROM module can be found in line 15, is named RAIDRST5.BIN, has the internal PCI ROM letter "B" and an uncompressed size of 119 KB.

Extraction of a PCI ROM module from a Phoenix/Award BIOS
General informations:

The extraction process will not remove anything from the mainboard BIOS file. Everything remains untouched.
If you want to know the PCI ROM version of any Phoenix/Award mainboard BIOS, you have to extract the related PCI ROM from the BIOS file.

Here is the description of the extraction procedure:

This is the CBROM command to extract any PCI ROM module from any Phoenix/Award mainboard BIOS file (without the angular brackets, but with the complete name of the mainboard BIOS file):
Source code

1

CBROM.EXE <name of the mainboard BIOS file> /PCI extract
After having executed the command, nothing will be extracted at this moment.
Usually there are more than 1 PCI ROM module within the BIOS. That is why the tool CBROM now lists all available PCI ROM modules of the BIOS and asks, which one of them shall be extracted.
Now you just have to edit the shown letter of the desired PCI ROM module (example: B) and then to hit "Enter".
This is what you will see:
After having done everything correctly the extracted PCI ROM file with its original name (here: RAIDRST5.BIN) can be found within the CBROM processing folder (C:\test).
If you want to know the version of the extracted PCI ROM module, you have to open it with a Hex Editor like HxD (>Link<). After having done it, you usually will see the name and the version of the PCI ROM module on the top right side of the Editor window:

This picture shows, that the extracted PCI ROM module has been the Intel RST RAID ROM v10.6.0.1091, when I have done the tests for this guide.
The EXTRACT command can be used not only for the PCI ROMs, but also for all other BIOS modules, which are listed by CBROM (except the sensitive modules "System BIOS" and "NCPUCODE"). The only difference is, that you have to replace the word "PCI" within the EXTRACT command by the short name of the related module you see on the left side of the BIOS structure overview shown by CBROM (XGROUP, ACPI, GROUP, SETUP0, TSEG0, YGROUP, OEM3, LOGO1, OEM0, GV3, MINIT, HTINIT, 2PE32 etc.). Even the modules of the different "HOLES" can be extracted this way.
Here are some command examples:
Source code

1

CBROM.EXE <name of the mainboard BIOS file> /TSG0 extract
Source code

1

CBROM.EXE <name of the mainboard BIOS file> /HOLE1 extract
Hitting the "Enter" button will not yet execute the extraction. CBROM will ask you to enter the exact file name of the related module you want to extract. You can find the file name within the BIOS structure overview on the right side of the line.
After having hit the "Enter" button, you will see the extracted file within the CBROM processing folder (C:\test).
Note: An extraction of several PCI and non-PCI modules may be necessary to recreate the original BIOS structure after having updated any PCI ROM module (see below).

Removal of a PCI ROM module from a Phoenix/Award BIOS
General informations:

Contrary to the extraction procedure the BIOS file will be altered by the release command.
Furthermore the removed module will not be stored within the CBROM processing folder.

Here is the description of the removal procedure:

Execute the following command (without the angular brackets, but with the complete name of the mainboard BIOS file):
Source code

1

CBROM.EXE <name of the mainboard BIOS file> /PCI release
After having done that the tool will present - as shown within the previous chapter - a list of all available PCI ROM modules and ask you, which of them you want to remove.
Edit just the shown letter of the PCI ROM module you want to be removed and hit the "Enter" button of your keyboard.
After having done that the related PCI ROM module will be removed from the BIOS file. Contrary to the extraction method the released module file will not be saved by CBROM.

Integration or Replacement of a PCI ROM module
General informations:

The CBROM command for the integration and for the replacement of a PCI ROM module is exactly the same.
According to my knowledge it is not only easier but safer too, if the PCI ROM modules are simply replaced within the mainboard BIOS file and not removed and inserted in different steps.
Simple reason: Only this way the user can be sure, that the location of the new PCI ROM module within the BIOS structure will remain the same as it was with the old PCI ROM module.
Important: To prevent any problem during the PCI ROM module replacement you have to make sure, that the new PCI ROM file has exactly the same name as the old one, which has been within the BIOS file before.
Within a certain bandwidth it is possible to replace a smaller sized PCI ROM module by a bigger one. The tool CBROM will compensate the size difference by its dynamic compression ability.
If the the new PCI ROM module is too big and there is not enough place within the BIOS file, you will get an adequate CBROM message.
Tip: Maybe you can create the needed space by removing an unneeded module like the OEM LOGO before you restart the PCI ROM replacement procedure.

This is what to do, if you want to insert or replace a PCI ROM module:

Run the tool CBROM and enter the following command (without the angular brackets, but with the complete names of the mainboard BIOS and PCI ROM files):
Source code

1

CBROM.EXE <name of the mainboard BIOS file> /PCI <name of the PCI ROM file>
Then you will see a picture like this one:

Don't worry about the shown percentage number lower than 100%, the file will be totally replaced.
If everything worked correctly, you will now find the "modded" BIOS file with the updated PCI ROM module within your processing folder (C:\test). The modded BIOS file should have exactly the same size and name as the original BIOS file, but an actual date.
Before you are going to flash the "modded" BIOS into your mainboard BIOS chip, you should verify, that the new desired PCI ROM has been properly inserted:
Open the modded mainboard BIOS file as written above.
The content of the "modded" mainboard BIOS will be shown like this example:

If you compare it with the content of the original BIOS file, you may realize, that the PCI ROM module now is listed somewhere else than before (example: now line 24 instead of line 15). Usually this is nothing to worry about. Important will be, that the related new PCI ROM module is only listed once, has the same internal name (here: RAIDRST5.BIN) and the same internal letter (here: B) as before.
Attention:
- A problem may occur by the checksum error sensitive module MINIT (file name: MEMINIT.BIN), if such module is present within the BIOS structure and the PCI ROM module you want to update is within any line above the MINIT module.
  Although the tool CBROM32_198 will remove and reinsert the checksum sensitive BIOS modules (MEMINIT.BIN, HT.DLL and HT32GATE.BIN) automaticly in this case, you should make sure, that this procedure has been done correctly. Most important is the exact offset position of the "MEMINITENTRYPOINT", which should be the same as within the original BIOS file.
  That is why I recommend to open the "modded" and the original BIOS file simultaneously by a hex editor and to compare the offset data of the "MEMINITENTRYPOINT". If it should not be identical, it has to be corrected, but without touching the checksum of the complete BIOS file.
- As I mentioned above, the tool CBROM is not able to replace any module without changing the internal BIOS structure. Each reinserted or replaced module will be shown at the bottom of the BIOS structure with the last=highest line number.
  Until now I am not sure, if this has any negative impact on the later BIOS flashing process, but it may be a good idea to completely recreate the previous BIOS structure by using the tool CBROM32_198. You just have to extract and to reinsert step-by-step all listed BIOS modules beginning with the updated PCI ROM going down the structure list until you got the original module order again. Check it with the cbrom <mainboard file> /D command!

C. Flashing the modded BIOS into the mainboard BIOS chip

It is strongly recommended to follow the following advices:

Before you are going to flash the new BIOS, you should make a complete backup of your entire system and boot partitions or at least of all important data. After having done that, enter the BIOS and list all your special settings. Before you leave the BIOS, choose and save the DEFAULT settings.
After having flashed the new BIOS, you have to redo your previous BIOS settings.
Before you restart with your usual PC work, you should verify the full function of the updated PCI ROM module. If you have inserted a new RAID ROM version into the BIOS, you have to make sure, that the "RAID" mode of the on-board SATA Controller is enabled, and then you should run the RAID Configuration Utility by hitting CTRL+I, F10 or similar (look into your mainboard manual).
Advice for users with a non-RAID system:
Users, who are running their SATA Controllers in AHCI or IDE mode, should check the function of the freshly updated RAID ROM module the same way. After having temporarily enabled the "RAID" mode of the on-board SATA Controller they should run the RAID Configuration Utility and look, if everything seems to be fine (but don't create a RAID array!). Then they can close the Utility and reset the SATA Controller to the usual setting (AHCI/IDE mode). The data of their AHCI/IDE system will not be altered or destroyed by this procedure.

Any feedback is much appreciated. Most important is a short report about the success or failure of flashing the "modded" BIOS into the BIOS chip of your mainboard. Don't forget to mention the vendor and name of your mainboard and the sort and version of the flashed PCI ROM module. You can write in english, french or german language.
If this guide was a help for you and you want to say "Thanks", you can hit the "Danke" button on the buttom of the start post.

Good luck!
Fernando

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

This post has been edited 29 times, last edit by "Fernando" (May 10th 2013, 9:34pm)

odiebugs

User

Posts: 52

Date of registration: Jul 9th 2012

Thanks: 0 / 2

3

Tuesday, July 10th 2012, 2:17am

First I have to say thanks, for such a great insightful and easy to follow thread. I thought all was lost until I read your post, can't thank you enough.

I want to buy the ASRock x79 extreme 7, its one of the only lga 2011 mobo's with a real sata 3 controller, but there is always some joke along with it.

I needed to change the Intel enterprise rom to a regular rom because I want TRIM to work in RAID. I modded the 1.30 BIOS, to the beta 11.5.0.1347 raid rom.

Now because of your awesome post I was able to replace the enterprise with the regular rom, and after I checked the BIOS with hex and it was replaced.

I can't test it because I didn't buy the MOBO yet, but because you made it so easy and I think I got it, I will buy it soon.

I hate to ask a question but if you ever get bored maybe you can help.

I want to replace the Marvell, but I am not sure about setting the link and checking the ID number like I did with the Intel on the MM tool.

So if ever have time to check and let me know what has to be done, I would really appreciate it.

The marvell rom is the 1.0.0.0025 in the BIOS, I am not even sure if the 1.0.0.1033 newer rom ( which is what I want to put in ) works on the 9182, that is on the MOBO.

Thanks again for such a great post.

This post has been edited 3 times, last edit by "odiebugs" (Jul 10th 2012, 10:01am)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

4

Tuesday, July 10th 2012, 12:11pm

@ odiebugs:

Welcome at German Win-Lite Forum!

Now to your plans and questions:

Quoted from "odiebugs"

I want to buy the ASRock x79 extreme 7, its one of the only lga 2011 mobo's with a real sata 3 controller, but there is always some joke along with it.
I needed to change the Intel enterprise rom to a regular rom because I want TRIM to work in RAID. I modded the 1.30 BIOS, to the beta 11.5.0.1347 raid rom.

The idea seems good, but I am not sure, that you will be totally satisfied, if you reaalize your plan.
Intel has developed the currently available Intel RAID ROM modules of the v11.5 series for their SATA RAID Controllers with the DeviceID DEV_2822 (= "Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller") and not for the X79 chipset DEV_2826 ones (= "Intel(R) C600 Series Chipset SATA RAID Controller"). As a consequence you may not get all storage features of the X79 chipset.
This is what I would do: I would buy a mainboard with an Intel Z77 chipset and - if needed - update the Intel RST RAID ROM to the latest version of the v11.5 or v11.6 series. After having built the new Intel Z77 system with 2 or more SSD's connected with the Intel SATA3 ports, I would create a RAID0 array. This way you will have the best chances to get the desired TRIM or UNMAP support even wihin the RAID members.

Quoted from "odiebugs"

I want to replace the Marvell, but I am not sure about setting the link and checking the ID number like I did with the Intel on the MM tool.
So if ever have time to check and let me know what has to be done, I would really appreciate it.
The marvell rom is the 1.0.0.0025 in the BIOS, I am not even sure if the 1.0.0.1033 newer rom ( which is what I want to put in ) works on the 9182, that is on the MOBO.

The user btester found, that the Marvell AHCI/RAID ROM v1.0.0.1033 contains the following string (readable by opening the file with a hex editor):

	Source code
1	DEVICE_ID_LIST = 9023,90A3,9110,9190,9111,9191,9120,91A0,9122,91A2,9123,91A3,9125,91A5,9128,91A8,9130,91B0

So it seems, that the Marvel 91xx SATA Controller with the DeviceID DEV_9182 will not be supported by this ROM version.
By the way: The procedure of the Marvell AHCI/RAID ROM update is quite similar to the procedure I have described within my guide (= start post). The VendorID of Marvell is 1b4b and the MMTool usually shows the Marvell 91xx SATA Controller with the DeviceID 9120 or 9123. Nevertheless all DeviceID's, which are listed within the CODE box, will be supported by the related ROM module. Additionally the firmware of the Marvell 91xx SATA Controller has to be updated by using a special firmware tool. The actual MV-91xx firmware is v2.2.0.1125b and can be downloaded from >this< site.

Regards
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

This post has been edited 2 times, last edit by "Fernando" (Jul 10th 2012, 12:13pm)

odiebugs

User

Posts: 52

Date of registration: Jul 9th 2012

Thanks: 0 / 2

5

Wednesday, July 11th 2012, 10:05am

Thanks Fernando, for letting me know about the devise ID.

I would rather let garbage collection do its thing, then to feed the thieves, crooks, at intel.

What kind of company puts pci-e 3.0 on an old lga 1155 CPU, but doesn't on a new lga 2011 CPU, *** CROOKS***.

Must be Gates sheep and Intel are still in bed together.

I can't post what these people really are, because if I did, I would get banned.

As for the Marvell 1033, I have opened it with hex, and on the right side, there is nothing about any of the models, only thing I see is 88SE91XX. I have even searched for 9128, 9182, and found nothing.

Strange.

I still think this post is the best, as I know I can use it in the future. Thanks again for such a helpful post.

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

6

Wednesday, July 11th 2012, 12:15pm

Quoted from "odiebugs"

As for the Marvell 1033, I have opened it with hex, and on the right side, there is nothing about any of the models, only thing I see is 88SE91XX. I have even searched for 9128, 9182, and found nothing.

You are right - my bad. The list of the supported DeviceID's is not within the ROM file itself, but within the file named hw_config.txt, which is part of the Marvell 91xx firmware pack v2.2.0.1125b containing the newest Marvell 91xx AHCI/RAID ROM v1.0.0.1033.
Here is the complete text:

	Source code
1 2 3 4	[SECTION] VENDOR_ID = 1B4B DEVICE_ID_LIST = 9023,90A3,9110,9190,9111,9191,9120,91A0,9122,91A2,9123,91A3,9125,91A5,9128,91A8,9130,91B0 [END]

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

odiebugs

User

Posts: 52

Date of registration: Jul 9th 2012

Thanks: 0 / 2

7

Wednesday, July 11th 2012, 8:18pm

You are never bad, lol

Thanks for the info.

Weird, its in the image creator folder.

Its also strange how station driver has the 1033 listed as 88se91xx, but has the 1028 listed as 9123/9128. But both firmware have the same HW.config file.

This is what happens when these company's abuse customers.

Marvell does not help customers, Intel has stopped it downloads for chipset drivers, via download center.

They should not waste their time with the 88se91 series, they are NOT a Sata 3 controller.

How about the 9220, another Sata 2 fake Sata 3 controller, they need to be sued for false misrepresentation along with the MOBO for using it and calling them Sata 3.

If a lot of people said something and stood up against being robbed, they would change their way's.
People are left waiting for the MOBO company to update, which is sad.

They don't care and leave up old drivers for a long time.

This post has been edited 1 times, last edit by "odiebugs" (Jul 11th 2012, 8:20pm)

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

8

Wednesday, July 18th 2012, 7:25pm

Hello and thanks for this thread :-)

I want to upgrade my Marvell ROM from 1.0.0.1025 to 1.0.0.1033.

The ROM is present on 3 locations in my Asys P7P55D-E 1504 bios ( the last one ) :

I tried to extract the 3 .bin, that worker, they are identical 1.0.0.1025 version.

How can I upgrade to 1033, must I replace the 3 ? Isn't it strange to have this bin 3 times in the same bios ?

I also found the Intel(R) RAID for SATA - v8.9.0.1023 inside this bios, where can I fin an update for this one ?

Thanks in advance from France ;-)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

9

Wednesday, July 18th 2012, 11:18pm

@ KevinNash:
Welcome at German Win-lite!

Quoted from "KevinNash"

I tried to extract the 3 .bin, that worker, they are identical 1.0.0.1025 version.
How can I upgrade to 1033, must I replace the 3 ?

Try it. If you will get an error message like "Unable to replace the module", remove 2 of them and then update the third one.
According to my knowledge you have to additionally update the Marvell 91xx Bootloader and the Marvell 91xx Firmware, which are listed by the MMTool in the lines ID E6 and ID E7. You can find the download links to the actual E6 and E7 modules within the start post of >this< thread.

Quoted

Isn't it strange to have this bin 3 times in the same bios ?

Yes, that obviously has been a mistake done by the mainboard manufacturer. There is no need for more than 1 PCI ROM module for a specific device (in your case DEV_9120).

Quoted

I also found the Intel(R) RAID for SATA - v8.9.0.1023 inside this bios, where can I fin an update for this one ?

>Here<.

Good luck!
Fernando

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

10

Thursday, July 19th 2012, 12:19am

Thank you for the aswer and the welcome Fernando :-)

I'll pass on the Marvell update, I have doubts because of the 3 modules and the E6 and E7 thing. I am too afraid to brick my mobo ;-)

If I extract my original E6 and E7, the don't look like the ones you provide on the download link.

Regarding my Intel ICH10R ROM update, can I use >Intel RST RAID ROM v11.2.0.1527< (für DEV_2822, d.h. ab ICH8R) ?

Actually I have the latest MSM ROM>Intel MSM RAID ROM v8.9.0.1023<

and Intel RST 11.2.0.1006 driver. I'll have a new SATA 6G SSD soon, will it improve performance or should I let things as they are ?

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

11

Thursday, July 19th 2012, 12:41am

Quoted from "KevinNash"

I'll pass on the Marvell update, I have doubts because of the 3 modules and the E6 and E7 thing. I am too afraid to brick my mobo

I can understand your decision.
Alternatively you can try to get the Marvell 91xx Controller updated by running the installer of the Marvell 91xx Firmware Update package v2.2.0.1125b (>Download link<).

Quoted

Regarding my Intel ICH10R ROM update, can I use >Intel RST RAID ROM v11.2.0.1527< (für DEV_2822, d.h. ab ICH8R) ?

If I were you, I would do it.

Quoted

Actually I have the latest MSM ROM>Intel MSM RAID ROM v8.9.0.1023< and Intel RST 11.2.0.1006 driver. I'll have a new SATA 6G SSD soon, will it improve performance or should I let things as they are ?

Yes, it will improve the performance of your system..

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

12

Thursday, July 19th 2012, 10:19am

Thank you again, that's an impressive support !

Do you suggest me 11.2.0.1527 or >Intel RST(e) RAID ROM v11.5.0.1414<
(für DEV_2822, d.h. ab ICH8R, Achtung: Dieses ROM-Modul gehört
eigentlich zur RST "Enterprise"-Serie, "passend": Intel RST(e)-Treiber
v11.5.x.xxxx, Dank an btester für den Link!)

I don't really understand the 11.5 version, I don't speak german at all sorry :'-(

Is it better to stay on the " classic RST " with 11.2.0.1527 ROM ?

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

13

Thursday, July 19th 2012, 4:55pm

Quoted from "KevinNash"

Do you suggest me 11.2.0.1527 or Intel RST(e) RAID ROM v11.5.0.1414

That question is not easy to be answered without knowing the details of your system and your pc work preferences.
Generally I would recommend the Intel RST RAID ROM v11.2.0.1527 and the RST drivers v11.2.0.1006 for users with an AHCI system, whereas RAID users may get more benefit by flashing the Intel RAID RSTe ROM v11.5.0.1414 and using the latest RSTe drivers of the v11.5 series.

Regards
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

14

Thursday, July 19th 2012, 8:01pm

Fine, I'll choose this one, it's for my new Samsung 830 SSD, with no RAID ;-)

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

15

Friday, July 20th 2012, 1:01pm

Done Fernando, BIOS modded and flashed with 11.2.0.1527 Intel RST(e) RAID ROM.

Is there a way to check this ROM version somewhere into windows or with a software ?

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

16

Friday, July 20th 2012, 1:27pm

Quoted from "KevinNash"

Done Fernando, BIOS modded and flashed with 11.2.0.1527 Intel RST(e) RAID ROM.

Congratulations!

Quoted

Is there a way to check this ROM version somewhere into windows or with a software ?

Usually the Intel RAID ROM version is only visible, if you are running your HDD/SSD in RAID mode.
You can test it this way:
1. Enter the BIOS and set the SATA Controllers temporarily to "RAID" - save this setting and reboot.
2. Hit Ctrl+I while rebooting.
Now you should see the Intel RAID ROM Utility with the version details. Don't change anything within this Utility!
You will get your AHCI system back by doing this:
1. Reboot and enter the BIOS again.
2. Set the SATA Controllers to "AHCI" mode.
3. Save the BIOS settings and reboot.

Regards
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

17

Friday, July 20th 2012, 9:21pm

That work perfectly ! I just checked and all is OK :-)

You clearly know what you are doing here, very impressive !

I saw in my bios 10EC:8168 PCI option ROM, that's my Realtek gigabit LAN

I see with HxD " Realtek PCIe GBE Family Controller Series v2.29 (06/30/09) "

Could it usefull to update this ROM too and do you know where I can fiind the .bin for that ?

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

18

Friday, July 20th 2012, 10:17pm

Quoted from "KevinNash"

That work perfectly ! I just checked and all is OK

That is good news.

Quoted

I saw in my bios 10EC:8168 PCI option ROM, that's my Realtek gigabit LAN
I see with HxD " Realtek PCIe GBE Family Controller Series v2.29 (06/30/09) "
Could it usefull to update this ROM too and do you know where I can fiind the .bin for that ?

AFAIK the "normal" users, who do not use the feature Wake-on-LAN or Power-on-LAN, won't get much benefit by an update of the Realtek PCI ROM module. That is why I do not recommend to update the Realtek ROM unless you have any problems with your LAN or Network connection.
You can get the latest Realtek PCI ROM version from >this< Realtek site within the section "DOS". Actual is v2.48 dated 07/06/2012. The packages include a flash utility.
Since I have never tried to update any Ethernet PCI ROM, I can give you no further advice regarding the update procedure.

Regards
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

This post has been edited 1 times, last edit by "Fernando" (Jul 20th 2012, 11:03pm)

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

19

Friday, July 20th 2012, 11:59pm

Fine, thanks for the advices, I let my LAN ROM it as it is now.

Isn't there a PCI ROM modules database somewhere ? I searched a lot and I don't found this kind of database on the web.

I want to update my Jmicron module JMB36X 197B:2363 as I did for the Intel one.

That update thing is addictive lol ;-)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

20

Saturday, July 21st 2012, 12:14am

Quoted from "KevinNash"

Isn't there a PCI ROM modules database somewhere ? I searched a lot and I don't found this kind of database on the web.

The only big PCI ROM database I found, is on >this< page, but you will not find really actual modules there. That is why I started >this< thread.

Quoted

I want to update my Jmicron module JMB36X 197B:2363 as I did for the Intel one.

It will not be a big problem for you. You will find the newest available JMB36x RAID ROM module v1.0.7.28 >here<.

Good luck!
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

21

Saturday, July 21st 2012, 11:27am

Quoted from "Fernando"

It will not be a big problem for you. You will find the newest available JMB36x RAID ROM module v1.0.7.28 >here<.

Mine is JMB36X 197B:2363 and your is for 197B:2362, apparently not exactly the seme device.

I have an idea, let's take Asus for example.

Can we know on which motherboard there is the same devices ?

We could take the latest mobo BIOS and extract the .bin by ourself.

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

22

Saturday, July 21st 2012, 12:04pm

Quoted from "KevinNash"

Mine is JMB36X 197B:2363 and your is for 197B:2362, apparently not exactly the seme device.

AFAIK all JMicron JMB36x Controllers (DEV_2360, DEV_2361, DEV_2362, DEV_2363, DEV_2364, DEV_2366, DEV_2369 and DEV_239F) are using the exactly same ROM module. So you probably can use the version I have linked without any problem.
Nevertheless I have replaced the JMB 36x RAID ROM module, which has been linked within the start post, by a file, which I found >here<. It has been extracted by ZioGTS from a BIOS of a mainboard with the DeviceID 2363.
By the way: The name of the ROM file will not change the DeviceID shown by the MMTool.

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

This post has been edited 1 times, last edit by "Fernando" (Jul 21st 2012, 12:27pm)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

23

Saturday, July 21st 2012, 12:31pm

@ KevinNash:

Please read my last post again, because I have edited it.
Since I have replaced the JMB 36x RAID ROM module, which was linked within the start post, I recommend to take the freshly uploaded one, if you want to be sure, that it will suit your system.

Regards
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

KevinNash

User

Posts: 9

Date of registration: Jul 18th 2012

Thanks: 0 / 1

24

Saturday, July 21st 2012, 2:42pm

OK, I'll test this week-end ank keep you informed.

Interesting thread found at bios-mod forum, I'll read it carefully.

I saw I can open Marvell BIOS setup by hitting Ctrl-M, I'll give it a try right now.

EasterEEL

User

Posts: 3

Date of registration: Jul 26th 2012

25

Thursday, July 26th 2012, 9:26pm

Many thanks for the guide it encouraged me to mod my Gigabyte G1.Sniper X58 bios and I have some questions before I flash it onto my system. All seems to have gone well and the two OROM's I have updated are:

Intel (RAIDRST5) to v11.5.0.1414

Marvell 9182 (91A2B) to v1.0.0.0025

Using CBROM21_198 I can't get the bios internal BIOS structure in the same order as I can only remove four items (A,B,C,D). So lines 14,15,16,17 are now 18,19,20,21 (see attachment). I noticed BIOS modders seem to be able to get the structure exactly the same so how would I do that and do I need to do that?

Also I wanted to confirm I don't need to do anything else for the Marvell 9182 controller update. There doesn't appear to be anything else to update in the bios but I am not sure if also need to update a bootloader and the controller firmware as well?

Any clarifcation gratefully received, thank you.

EasterEEL has attached the following image:

This post has been edited 4 times, last edit by "EasterEEL" (Jul 26th 2012, 9:55pm)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

26

Thursday, July 26th 2012, 9:55pm

@ EasterEEL:
Welcome at German Win-Lite!

Quoted from "EasterEEL"

Using CBROM21_198 I can't get the bios internal BIOS structure in the same order as I can only remove four items (A,B,C,D). So lines 14,15,16,17 are now 18,19,20,21. I noticed BIOS modders seem to be able to get the structure exactly the same so how would I do that?

You can do that by removing and reinserting all modules, which are in a wrong order, but I don't think, you need to do that, because the sensitive module MINIT obviously has been above the PCI ROM modules, before you updated the Intel and Marvell PCI ROM modules.
This is what I have written within my guide:

Quoted from "Fernando"

A problem may occur by the checksum error sensitive module MINIT (file name: MEMINIT.BIN), if such module is present within the BIOS structure and the PCI ROM module you want to update is within any line above the MINIT module.

Quoted from "EasterEEL"

Also I wanted to confirm I don't need to do anything else for the Marvell 9182 controller. There doesn't appear to be anything else in the bios but I don't know if also need to update a bootloader and firmware as well.

It may be possible, that you have to update the Marvell 91xx bootloader and the firmware as well, but they are not easy to find within your BIOS. I doubt, that you will run into problems regarding this point.
So I would flash the mainboard BIOS as it is. Regarding the Marvell 91xx Firmware I recommend to download the newest version for your DEV_9182 Controller and flash it separately into the Controller using the DOS installer.

Regards
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

EasterEEL

User

Posts: 3

Date of registration: Jul 26th 2012

27

Friday, July 27th 2012, 5:57pm

Quoted from "Fernando"

Regarding the Marvell 91xx Firmware I recommend to download the newest version for your DEV_9182 Controller and flash it separately into the Controller using the DOS installer.

Thanks for your help. Am I right in thinking that this Marvell 9182 controller firmware update is desirable but completely independant of the 91A2B.bin update to the BIOS?

I think the 9182 controller is referenced as 91A2 in the hw_config.txt and the latest firmware update for the Marvel 9182 controller is this one:

marvell_88se91xx_firmware_2.2.0.1125b(www.station-drivers.com)

Have I got that right, thx?

This post has been edited 4 times, last edit by "EasterEEL" (Jul 27th 2012, 6:14pm)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

28

Friday, July 27th 2012, 6:48pm

Quoted from "EasterEEL"

Am I right in thinking that this Marvell 9182 controller firmware update is desirable but completely independant of the 91A2B.bin update to the BIOS?

It seems not to be really independent, because you should update the suitable Marvell 91xx bootloader, the firmware and the PCI ROM module at once.
The normal procedure is to run the DOS installer of the Marvell 91xx Firmware Pack, which contains all 3 needed modules, but unfortunately some mainboard manufacturers have blocked the PCI ROM update this way.
So the alternative way is to flash all 3 modules into the BIOS by using CBROM.
These are the actual 3 Marvell modules, which you should get into the BIOS file:
1. Marvell 91xx Bootloader v1.0.1.0002b, can be downloaded from >here<
2. Marvell 91xx Firmware v2.2.0.1125b, can be downloaded from >here<
3. Marvell 91xx AHCI ROM v1.0.0.1033, can be downloaded from >here<

Quoted

I think the latest firmware update for the Marvel 9182 controller is this one:
marvell_88se91xx_firmware_2.2.0.1125b(www.station-drivers.com)
and the 9182 controller is referenced as 91A2 in the hw_config.txt. Have I got that right?

Yes, that is correct. You can get the complete Marvell 91xx Firmware Pack v2.2.0.1125b also directly from >here<.

If you should not succeed with the Firmware update by using the DOS tool of the Firmware Pack v2.2..0.1125b, I recommend to do the following:
1. Extract all modules of your BIOS, which may contain the Marvell xx bootloader or the Marvell firmware (all "GROUP ROM" and "OEM CODE" modules) by using the tool CBROM and choose a name like you see them within the CBROM window for the related madule.
2. Open the extracted modules with a Hex Editor und compare the content with the 2 previously downloaded and unzipped actual Marvell Bootloader and Firmware modules.
3. Once you know, which modules of your BIOS do contain the Marvell 91xx bootloader and the Marvell 91xx firmware, you can update all 3 Marvell 91xx modules at once by using CBROM.

Good luck!
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

EasterEEL

User

Posts: 3

Date of registration: Jul 26th 2012

29

Saturday, July 28th 2012, 1:31pm

I am struggling with the Marvell 9182 controller update because after extracting all modules from the f4e BIOS I cannot match up any of them using the Hex Editor to the Marvell 91xx Bootloader v1.0.1.0002b, the Marvell 91xx Firmware v2.2.0.1125b or Marvell 91xx AHCI ROM v1.0.0.1033. The files are completely different.

The f4e BIOS contains v1.0.0.0017 firmware (module 91A2B.BIN size 137k) and I can easily match up v1.0.0.0025 (size 131k) firmware using the Hex Editor. The Marvell 91xx AHCI ROM v1.0.0.1033 looks completely different (size 28k). Additionally I can't find any extracted modules resembling the Marvell 91xx Bootloader v1.0.1.0002b, the Marvell 91xx Firmware v2.2.0.1125b is it possible these two modules are not in the f4e BIOS?

I am tackling this myself as the G1.Sniper motherboard has a small user base with little chance of Gigabyte providing updates now, but there are a few of us interested in using the Intel controller with RAID0 and TRIM. I am also interested in the Marvell 6GB controller which apparently does pass TRIM with MSAHCI drivers for non RAID, but Marvell are not helpful about firmware version info so I think it is worth updating the v1.0.0.0017 firmware to a more recent version.

Any futher help appreicated but I do understand you may not be familiar with this particular motherboard.

This post has been edited 2 times, last edit by "EasterEEL" (Jul 28th 2012, 1:33pm)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

30

Saturday, July 28th 2012, 2:01pm

@ EasterEEL:
Thanks for your report regarding the update of the Marvell 91xx SATA3 Controller modules.
Under these circumstances you should not flash any Marvell module into the BIOS of your mainboard.

Quoted from "EasterEEL"

Any futher help appreicated but I do understand you may not be familiar with this particular motherboard.

That is true.
This is what I recommend to do:
1. Update the Intel RAID ROM module of the latest G1.Sniper BIOS F4E and flash the modded BIOS into your mainboard BIOS chip according to my guide.
2. Download the "Marvell Storage Utility" package, which Gigabyte is offering for your mainboard (>LINK<) and execute the EXE file.
3. Install the actual Intel and Marvell 91xx SATA drivers.

Good luck!
Dieter

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

adb

User

Posts: 7

Date of registration: Sep 10th 2012

Thanks: 0 / 1

31

Monday, September 10th 2012, 1:32pm

im writing this on my phone so please excuse.

i folowed the ami guide and replaced the intel and jmic opt roms

jmic updated ok but intel has disappered im using the latest asus p6t bios. not se or deluxe or anything just p6t.

i noticed that the size field in mmtool after replacing the intel rom chanfed to the exact same hex size as the modulefiled above it
the field was something like user defined - dynamic but as i said it has the exact same size as the intel updated size?

if that means anythjng?

i flashed from ez flash 2. after i selected raid in the bios trying to bring up the intel opt rom config screen it now just wont go any further im confident ghat after i bios reset i shouls be able to get back in bios setup and reflash

but what was the problem with the inrel rom not installing?

ghanks

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

32

Monday, September 10th 2012, 1:49pm

@ adb:
Welcome at German Win-Lite!

Quoted from "adb"

what was the problem with the inrel rom not installing?

It is impossible to answer without knowing the Intel RAID ROM version you have inserted into your mainboard BIOS.

Regards
Fernando

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

adb

User

Posts: 7

Date of registration: Sep 10th 2012

Thanks: 0 / 1

33

Monday, September 10th 2012, 1:56pm

Intel RST RAID ROM v11.2.0.1527

thanks for the welcoming ans excelent info

i inserted 11.2.0.1527 :-)

edit: i should of added also im using the latesr p6t bios 1408 and included the only jmic opt rom avalible at the linked thread

This post has been edited 1 times, last edit by "adb" (Sep 10th 2012, 2:17pm)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

34

Monday, September 10th 2012, 2:23pm

Quoted from "adb"

i noticed that the size field in mmtool after replacing the intel rom chanfed to the exact same hex size as the modulefiled above it
the field was something like user defined - dynamic but as i said it has the exact same size as the intel updated size?
if that means anythjng?

Do you mean the "Size in ROM" dates within the line with the ID "F2" ("User defined or Reserved"). I don't think, that the similarity has something to do with your problem.
Maybe the on-board Intel SATA RAID Controller of your mainboard does not accept the newest RST RAID ROM module of the v11.2 branch.
Nevertheless I just have downloaded the latest BIOS 1408 for your ASUS P6T and replaced the original Intel MSM RAID ROM v8.0.0.1038 by the Intel RST RAID ROM v11.2.0.1527. The size of the Intel RAID ROM inside the BIOS changed dramatically from 65536 KB to 121856 KB.
If you want, you can test the BIOS, which has been modified by me (Note: Only the Intel RAID ROM has been replaced). You can download it from >here<. Before you flash it, I recommend to rename the file to the orginal one.
If you should run into the same problem as before, I recommend to replace the Intel RAID ROM module of your BIOS by an older Intel RST RAID ROM version (e.g. v10.1.0.1008).

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

This post has been edited 2 times, last edit by "Fernando" (Sep 10th 2012, 2:42pm)

adb

User

Posts: 7

Date of registration: Sep 10th 2012

Thanks: 0 / 1

35

Monday, September 10th 2012, 2:38pm

I will try your bios right after work and let you know, thanks for the quick reply

ill also send you my creation so you can check if its ok

This post has been edited 1 times, last edit by "adb" (Sep 10th 2012, 2:44pm)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

36

Monday, September 10th 2012, 2:48pm

Quoted from "adb"

Would also pre modding a Asus slic to it affect anything?

Each additional modding procedure may have an effect on the usability of the finally flashed BIOS.
Nevertheless I believe, that either the Intel RAID ROM v11.2.0.1527 is not compatible with your on-board Intel SATA RAID Controller or you have done something wrong while modding the BIOS file.

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

adb

User

Posts: 7

Date of registration: Sep 10th 2012

Thanks: 0 / 1

37

Tuesday, September 11th 2012, 4:39am

If you have the time could you make another one also including the jmic opt?

That way I can compare the CRC and see if I'm doing anything wrong. But I guess I can do the same with the one you provided anyway but that will help me check the jmic too

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

38

Tuesday, September 11th 2012, 11:18am

Quoted from "adb"

If you have the time could you make another one also including the jmic opt?

>Here< is the link to the BIOS, which now contains the Intel RAID ROM v11.5.0.1527 and the JMicron JMB 36x RAID ROM v1.0.7.28.

Good luck!

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

adb

User

Posts: 7

Date of registration: Sep 10th 2012

Thanks: 0 / 1

39

Tuesday, September 11th 2012, 12:17pm

thanks, it didn't work same thing happened,

when i did it myself however i got a different crc then the files you provided, maybe i did something wrong? or did you go a step further and optimize something in there that could explain it?

I think i just figured that out myself it's the name used when doing the replace, so i guess i followed your directions correctly.

This post has been edited 1 times, last edit by "adb" (Sep 11th 2012, 12:21pm)

Fernando

Easy RAIDer

Posts: 4,234

Date of registration: Oct 2nd 2008

Thanks: 893 / 20

40

Tuesday, September 11th 2012, 12:55pm

@ adb:

Some ASUS P6 boards have a 120 KB limitation regarding the RAID ROM modules (look >here<). That is why I suspect, that it is the big size of the actual Intel RAID ROM modules, which may have caused your problem while trying to flash the modded BIOS.
You can test it by replacing the Intel RAID ROM module by the much smaller sized v10.1.0.1008.
If you should succeed this way, you may ask ASUS for an updated BIOS for your mainboard without the 120 KB OROM limitation.

@ alle Anwender, die ihrem betagten Mainboard eine bessere Performance entlocken wollen:
Wer sich die Aktualisierung von bestimmten BIOS-Komponenten (sogen. PCI ROM-Modulen) zutraut, aber nicht genau weiß, was man dafür benötigt und wie es geht, sollte sich mal in >diesem< Bereich des Forums umsehen.

	Source code
1	CBROM.EXE <name of the mainboard BIOS file> /PCI extract

BIOS-Modding: How to update PCI ROM modules of an AMI/Phoenix/Award BIOS

Source code

Source code

Source code

Source code

Source code

Source code

Quoted from "odiebugs"

Source code

Source code

Quoted

Quoted

Quoted

Quoted

Quoted

Quoted

Quoted

Quoted from "Fernando"

Quoted from "EasterEEL"

Quoted

Intel RST RAID ROM v11.2.0.1527

Similar threads

Used tags