Thanks. So how i can find it? In CSMCORE I only have NV(1050 & df4), 1969:1083 and Intel(116, 1502 & 1503). With this MMTool and another EFI BIOS (P8H67-I) all works fine. btw thanks for a great ROM collection
Hi everyone, I'm planning to OROM mod my Asrock G31M-GS R2.0 BIOS (v1.80) in order to get AHCI and RST available on it (for a future SSD). I dumped the BIOS with the help of AFUDOS, opened with MMTool and extracted the only Intel OROM inside: Intel Q33 Q35 G33 PCI Accelerated SVGA BIOS Build 1533. Since I don't need/use the IGP, I'm wondering if I could replace this OROM by a RST one that is compatible with the ICH7 and by the way modifying the DeviceID by 27C1 to fake a ICH7R for the drivers. So, what you think? Will it work or will this lead to a complete brick of my mobo and this the worst idea ever ? Thanks for your help. PS: Sorry for my English I'm not a native speaker. edit Well, after reflection it's a bad idea. Now I'm figuring out if it could be possible to just insert it in the BIOS? Image of the MMTool list : h**p://tof.canardpc.com/view/a701fe37-ff2a-4841-80d9-a2acba07dbd9.jpg
Hi, chchatzop, I have the exactly same ASUS P5K Pro + OCZ Agility 3 and BSOD while completing Windows 7 installation. Have you found a solution yet?
ASUS P5Q Deluxe + OCZ Vertex 3 => BSOD when finishing Windows 7 installation....... RMAed Vertex 3 and got a new SSD. The new Vertex 3 did not BSOD and Windows 7 installation ok....
Hi, everyone! I am wondering how to upgrade the ASmedia 106x SATA ROM on ASUS P8Z77-V Pro. With Fernendo's guide, it is easy to upgrade its Intel ORom. But if we look into the CSMcore module of the 1504 Bios, we see three things, 8086:1502, 8086:162, and 8086:282a. None of these matches the asmedia numbers. So how could we upgrade the ASmedia 106x SATA ROM on ASUS P8Z77-V Pro? Thanks!
You can insert it in there using the MMtool. Somewhere else it was mentioned the previous BIOS had it, so I put it back there for the 1504 and now it shows ROM during boot (0.951). I have no idea if it actually changes anything seeing as I think it's IDE anyhow with no AHCI/RAID options (Z77-V), maybe that's why they removed it.. no point/use.
Ok that's good news, didn't want IDE only. Still unsure though if it's needed. Just comparing the modded BIOS vs. original there are ~200 lines more in the modded one. Changes are 11.5 OROM, newer Vbios and this now.
Hey guys, I have a Tyan S7025 board with an ICH10R chipset. I'm pretty experienced with BIOS modding it, as I've replaced the full-screen logo, the small AMI logo, and injected a SLIC table in the past. The ROM file is 4MB, and to open it with MMTool, you have to cut out the last 2MB of the ROM into a separate file. After editing, you prepend 2MB from the start of the original ROM file back onto the edited file, so you end up with a 4MB ROM file again. You can then flash that using AFUDOS. Anyway, I tried that method to replace the old 10.1 RST Option ROM with the latest 11.5 OROM, to gain TRIM support in RAID-0. However, when I flash that and set the ICH to RAID mode, the OROM doesn't load at all, I just get a flashing underscore in the top left corner of the screen. Now the big issue is this. I tried flashing the plain Tyan BIOS after that, and I get the 10.1 OROM to show, I can enter the RAID settings, etc., but it does not boot after that. It just hangs at "Press CTRL+I to enter configuration utility". The only way I can boot is by changing to AHCI mode, but my boot volume is on a two-SSD RAID-0 array, so I've now effectively locked myself out from normally booting to Windows. What I'm guessing has happened is the presence or the attempt to load the RST 11.5 OROM has somehow corrupted some configuration memory in the ICH chip that the RST 10.1 OROM now chokes on when trying to load. Does anyone have any idea what could have happened or how I could get the 10.1 OROM to work again? It feels like I've properly bricked my ICH It's always a risk and you know what could go wrong but this is only the second time that I've ever bricked something in such a way that I can't fix it myself without outside help. Thanks in advance! EDIT: I've done some more testing, and it seems whatever is making the 10.1 OROM choke is probably contained on the SSDs. Probably the array version got upgraded which is now causing troubles for the older firmware. When I boot up with only one disk instead of two (broken array) I can get through POST fine, however if I so much as hot plug the second disk while I'm in the config utility, the whole system freezes again as soon as I exit the utility. I'll run more tests tomorrow.
Never had this problem, but if config screen shows you a broken array, you don't have much to do but format...
What I meant was that I could get through POST (as in boot from USB stick etc) if I unplugged one of my two disks. Of course that is going to temporarily break the array. However, I tried to reproduce that today and couldn't get through POST in any way other than not having ANY disks plugged into the controller. My plan from yesterday was to get a Windows up and running on a spare non-RAID hard disk I have lying around, however even with that non-RAID disk connected (as the only disk, nothing else) I cannot get through POST. So there goes my theory that the disks were somehow the culprit.
Hy! I have ASUS P6X58D-E motherboard, with Marvell 9128 controller on it. I did mod with latest bios and firmware, but from day one, DEVICE ID is pointed at 9123 chip! The original driver from Marvell's homepage only has aoutoload.bin and any other file referred to 9123, not 9128 chip! How can I make image file for 9128 (or modules 20, E6, E7), so DEVICE ID is 9128. Everything is working OK, but it bothers me wrong "name" of Marvell controller. Thanks!!!