ASUS Commando BIOS 1901 Modded Well tried the modded Bios and everything seems too work. So my ASUS Commando is now running Intel Rapid Storage Technology Option ROM v10.0.0.1046, JMicron_JMB363 v.1.08.01_raid, and Marvell_Yukon_PXE v.6.60.2.3 for both LAN's. Now if someone could help with the Memory_Sizing update problem due to space that would be great! MOD BIOS 1901: h**p://***.sendspace.com/file/1hypks
I can tell you for sure most of modded BIOSes aren't test for ALL OROMs functionality. Even if MMtool can replace any module with any sizes which fit 1/2M BIOSes noone can guarantee now OROM configuration will work altogether. For example: 9.x/10.x Intel works fine but prevents working NIC/LAN/ OROM. Just no screen to "boot on LAN" in boot time. Most even don't know what's it but everyone must know that any now OROM version can influence the rest ones. only TESTs. Set ALL OROMs to enable and observe all screens from ALL OROMs on default BIOS: Intel's (Ctrl+I), Some ODD (CD/DVD) screen, NIC/LAN boot options and so on for all 20_xxxx.rom (orom) files in BIOS. Then start modding one by one testing the OROM screens for functionality. And remember - dummy replacing with some new OROM version can make the rest presenting OROMs useless - just wasting your BIOS space cuz they can and will for sure be inaccessible by some reasons. Test only can show this. My prev. posts here show this kind of situation with 9.6/10 Intel OROM and P5Q MoBo. And know for sure - OROMs are used on boot time only (for detecting h/w or for basic operations on later detected ones). They won't speed your PC - it's up to drivers business not middleware like OROMs.
* Updated with succes with the new INTEL Option Rom 10.0.0.1046 with : ASUS --> P5E WS PRO GigaByte --> GA-X58A-UD5 Pierre
Same here ( 10.0.0.1046 ) ASUS Rampage Formula BIOS 0001 RAID0 2x ST31000528AS ASRock X58 Extreme3 BIOS 2.20 RAID0 2 x ST3500418AS
If only you would know what OROM stand from and what's the difference between firmware and BIOS then you would deleted your stupid last message, noob. OROMs aren't firmware. They not stored on chip or ROM of specific chip. It's preboot middleware, noob. Read again: for basic initialization. To make BIOS see your dummy SSDs and boot system from them.
Updating LAN OROM's to lastest solves the problem of them not working with the 9.x/10.x Intel ROM. Older Marvell Lan ROM's not working with the 9.x Intel ROM is a know issue. The newest Marvell ROM's for my board are fully functional but only show up if they are set to enable and selected to boot before the hard drive or other boot device. They detect network cable, MAC address and attempt to boot then times out and goes to next boot device in boot list. As far as the memory_timings still need to make some room for them. Any suggestions on the next step to look at to acheive the task? If there is any padding that can be removed to make the room? Next step after that is to look at the memory test to see if it is up-gradeable. Currently there are 2 tests one for up to 4 gb and one for over 4 GB. Any productive thoughts welcome. Thanks
Asus P6T - Intel 10.0.0.1046 option ROM Asus P6T BIOS 1303 works with the 10.0.0.1046 Intel storage controller option ROM.
not every board has Marvell NIC. Atheros is on my one and has problems with latest intel oroms using together. Either this is a sizing limits or buggy orom thet refuses work with newer intel orom. Marvell has good support of their drivers and it's premium class chips (NIC) so they have to release nicely written OROMs. The rest vendors alas worse and thus these problems with OROMs compatibility arise. Either it's 1/2M bios sizes limitations or bad written oroms, who knows. But if you need all 100% working oroms then they should be tested each and every one (by booting them). Or some can be just a waste of space but with 10 Intel OROM which is doubtful advantage if you don't do any RAID array operations on pre-boot mode (Ctrl+I). My one is 8.9.1 the latest which Atheros NIC allows me to use w/ 100% functions on board. I see no joke here only stupid sarcasm not based on true knowledge. FYI: firmware is stored in (EEP)ROM of particular h/w (of chip-vendors). Not in MoBo BIOS which has nothing related to firmware (except for cases when CPU microcode updated.) I updated my firmware on following devices: CPU (microcode public distribution for C2D/C2Q), HDDs (microcode), VGA card (here BIOS is the true firmware for vga cards), ODD (CD and DVD modded firmware), maybe the rest. So if you have no more jokes about your lack of true knowledge on things you don't understand then erase your stupid sarcasm above, i mean it.
They firstly distributed as win KB936357, then bioses incorporated this with new builds. It's famous TLB bug patch.
Beware v10.0.0.1046 Option ROM on P6T Deluxe. I spent 4 hours to backtrace my bluescreen errors, until I got 9.x back on my bios... Even newer drivers does NOT work on P6T Deluxe.
A few modules new: Sep 2010 memory sizing module 15 (ddr2) and asus EZ Flash 2 utils F5: V3 is found on S775 boards, V4 from S1156. So use V3 for pre s1156 boards. Also should be mentiond: from v3 teste not all could detect bios brand string of MoBo (mobo model), however all worked fine in updating from EZ flash 2 from flash drive - this the only found issue.
FIY OROMs are real-mode code executed at pre-boot Your 48h are just common stability and OS testings. OROMs tested only by executing and direct using it, let's say you <Ctrl+I> and create/remove new RAID array in pre-boot env. Does anyone know 0x15 bios module is chipset-related or platform related? On s1156 15 modules not found, but found on s775 with both DDR2/DDR3 MoBo as well as on combined ones (DDR2+DDR3). [+]Found 10'Nov memory sizing module (15). Works w/ DDR2 (s775). Not tested on DDR3 but can probably work.
How wrong you are... An Option ROM typically consists of firmware that is called by the system BIOS. The bios you are telling about is the motherboard one. Devices depend deeply from firmware, both for bug fixes and for perfomance.
So your BSODs were caused by OROM or drivers? And why PnP OSes need drivers if bios has OROMs?) OROMs has the same meaning as bios - to allow you to detect device on boot and to boot some real-mode app with bios-like window with basic controller capabilities and modes w/o using real OS and/or vendor OS drivers for that. Nothing in 32/64 bit goes thru real-time boot code. Or...?
Thanks for all updated oroms... for info ezflash module v 3.36 works fine on rampage formula bios and without any issues, all others give issues. Benifit in updating ezflash module is in geting new function like ability to read bios files from harddisks in raid and NTFS file system. I did not try that memory sizing modules because i they can only mess up things, considering they are for eaglelake (p45) chipset and i have bearlake (x48) chipset. I dont want to brick my mobo again and messing up with memory modules seems like a great way to do exactly that