Page 2 of 14
#16 RE: [Guide] AMI (non-UEFI) BIOS Modding by Fernando 25.01.2014 10:25

avatar

@ Deccal:

I suspect, that the 120KB sized OROM module is too big for your X58 chipset mainboard BIOS.
The last less than 100KB sized Intel RAID ROM module is v10.1.0.1008, but it doesn't support Trim in RAID0.

#17 RE: [Guide] AMI (non-UEFI) BIOS Modding by Deccal 26.01.2014 14:40

I meant that when I turn on the computer the screen is black and no beep. Is there anything that I can do to restore my bios? I got a backup of my old bios.

#18 RE: [Guide] AMI (non-UEFI) BIOS Modding by Fernando 26.01.2014 14:48

avatar

Zitat von Deccal im Beitrag #17
I meant that when I turn on the computer the screen is black and no beep. Is there anything that I can do to restore my bios? I got a backup of my old bios.
Yes, you should be able to reflash the original BIOS, but if you have another computer, I recommend to update the Intel RAID ROM to v10.1.0.1008 and to flash the BIOS, which contains this more actual Intel RST OROM.

#19 RE: [Guide] AMI (non-UEFI) BIOS Modding by Deccal 26.01.2014 14:58

Is there any guide on how to do it?

#20 RE: [Guide] AMI (non-UEFI) BIOS Modding by Fernando 26.01.2014 15:09

avatar

Zitat von Deccal im Beitrag #19
Is there any guide on how to do it?
What do you mean, the OROM update or the BIOS extraction/flashing procedure?
The procedure is the same as you did it before. Only difference: You replace the Intel MSM RAID ROM of your original BIOS file by the Intel RST RAID ROM v10.1.0.1008 (instead of the "Especially modified Intel RST(e) RAID ROM v11.6.0.1702 with TRIM in RAID0 for ICH10R systems").

#21 RE: [Guide] AMI (non-UEFI) BIOS Modding by Deccal 26.01.2014 15:12

I meant bios, how can I does the recovery process work

#22 RE: [Guide] AMI (non-UEFI) BIOS Modding by Fernando 26.01.2014 15:26

avatar

Zitat von Deccal im Beitrag #21
I meant bios, how can I does the recovery process work
At first step you should clear the CMOS. If you should still not be able to enter the BIOS after having done that, I recommend to read >this< thread.

#23 RE: [Guide] AMI (non-UEFI) BIOS Modding by Oli_be 27.01.2014 02:11

@Deccal

Have a look at this thread. If the Boot Block of your BIOS is not damaged, this procedure could fix the problem. If your PC is not equipped with a Floppy Disk Drive (which is probably the case), it's explained that it's possible with a USB Flash Drive as well.

#24 RE: [Guide] AMI (non-UEFI) BIOS Modding by Gannet 20.06.2014 21:10

avatar

Hello, Fernando. I'm trying to update Intel Matrix Storage Manager option ROM v8.0.0.1038, which is in my Asus P5Q3 mobo, to the latest Intel RST(e) RAID ROM v13.1.0.2126 founded here. But the problem is that it doesn't enough space to replace it. I tried to delete OEM Logo module but the space still not enough. Which module at all can be safely removed from BIOS? In mine the following ones is in:

15 Memory Sizing
15 Memory Sizing
11 P6 Micro Code
2C User Defined or Reserved
08 Bootblock - runtime interface
FD User Defined or Reserved
30 User Defined or Reserved
FC User Defined or Reserved
0C ROMID
1B Single Link Arch BIOS
F2 User Defined or Reserved
20 PCI Option ROM
F5 User Defined or Reserved
21 Multi Language
21 Multi Language
20 PCI Option ROM
04 Setup Client
21 Multi Language
20 PCI Option ROM
0E OEM Logo
18 Display Manager
1E Reserved
19 Font Module
1A Small Logo(s)
06 SMBIOS
2B User Defined or Reserved
80 Image Information

Thanks.

#25 RE: [Guide] AMI (non-UEFI) BIOS Modding by Fernando 20.06.2014 22:20

avatar

Zitat von Gannet im Beitrag #24
I'm trying to update Intel Matrix Storage Manager option ROM v8.0.0.1038, which is in my Asus P5Q3 mobo, to the latest Intel RST(e) RAID ROM v13.1.0.2126 founded here. But the problem is that it doesn't enough space to replace it. I tried to delete OEM Logo module but the space still not enough. Which module at all can be safely removed from BIOS?
According to my knowledge it will be useless to remove any other module - you will not win the needed space for a 120 KB sized Intel RAID ROM module.
As you can see >here<, our Forum member hanson has tried everything to get any of the up-to-date Intel RAID ROM versions inserted into the ASUS P5Q3 DeLuxe BIOS, but got a failure with all of them.
That is why I recommend to update the Intel MSM RAID ROM v8.0.0.1038 to the Intel RST RAID ROM v10.1.0.1008. Since this version has an uncompressed size of 85 KB, it will not be a problem to get it inserted into the BIOS and properly working after having flashed the modded BIOS. All later released Intel RAID ROM modules have an uncompressed size of not less than 119 KB.

#26 RE: [Guide] AMI (non-UEFI) BIOS Modding by Gannet 20.06.2014 23:34

avatar

Thank you very much, Fernando, for advice. I'll update to v10.1.0.1008.

P.S. BTW, I have JMicron JMB36x RAID ROM modul v1.8 if you need to post it here.

#27 RE: [Guide] AMI (non-UEFI) BIOS Modding by Fernando 20.06.2014 23:44

avatar

Zitat von Gannet im Beitrag #26
I have JMicron JMB36x RAID ROM modul v1.8 if you need to post it here.
I am always interested in new RAID ROM modules. Which is the exact version number?

#28 RE: [Guide] AMI (non-UEFI) BIOS Modding by Gannet 21.06.2014 00:15

avatar

Here it is: jmb363_1.08.01.7z. Founded it last year or even earlier. As I remember, noted that this version was removed from site because of slow external SATA performance as a result. Didn't tested external SATA but on my previous P5B Deluxe mobos it worked well unlike most of other older versions which causes hangs recognizing HDD during POST.
P.S. Also there is P5B Deluxe ROMs updated BIOS (by me) with:
1) Intel_RST_RAID_ROM_v10.1.0.1008
2) jmb363_1.08.01
3) Marvell_LAN-ROM_DEV-4380_v6.68.1.3
...if anyone interested.

#29 RE: [Guide] AMI (non-UEFI) BIOS Modding by lordkag 21.06.2014 19:45

avatar

I think this 1.08.01 is older than 1.07.28, being just a test branch that was abandoned. Not only the year is older - 2009 vs 2010 - but there are reports about not fully working (here and here). Not even JMicron site has them anymore.

But since 1.07.28 has its bugs, I suppose it is up to user choice to test them.

#30 RE: [Guide] AMI (non-UEFI) BIOS Modding by mockingbird 03.11.2014 04:13

Zitat von Fernando im Beitrag #1
•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.


Fernando.

I'm stuck with an Asus P5B and trying to install Windows XP x64 on it with AHCI enabled.

The problem is that no matter which F6 driver I use, I get a 0x0000007b in the text mode setup part.

I think the problem is that Asus made a mistake when they defined the onboard controller as 2822, because the chipset is ICH8 and NOT ICH8R. When setup tries to run the iaStor.sys on the wrong chip, it BSODs. This is a common problem with the P5B and its variants, and I have not yet found a way around this.

I thought about modifying the Dev ID to 2821 with MMTool, but I don't know if this is possible.

Can you please have a look at the BIOS for me?

http://dlcdnet.asus.com/pub/ASUS/mb/sock...B-ASUS-2104.zip

Thanks

edit1: I just ran a low-level PCI ID util from Ultimate Boot CD, and it is showing device 2824 as well, so I wonder if I should target my F6 towards that device. The problem is that your updates F6 disk does not work. It just freezes when I use it in the XP x64 setup. If you could take a look at that I'd really appreciate it. I tried hex-editing the DEV 2822 to DEV 2821 with a hex editor. Succeeded in changing the DEV ID, but did not help.

edit 2: YES!

I got it to work by slipstreaming your universal driver onto the CD and targetting for DEV 2824 instead of 2822.

Thanks again Fernando!

Xobor Forum Software von Xobor
Datenschutz