bios modding is very old , at the time of pentium 2 - 3 it started to be popular ...UBU is very good but from what i know works like softwares from the beginning . the guid system is very good for bios modding and prevents errors in rom choice :] that is the main thing of UBU to have a stock of rom : the good thing of this tool . sadly , for CPU microcodes , they use hand made files [...while there are very good officials "databases" available for free...] , and even when choice is wisely "made by hand" and the bios file created with bios-maker AMI : i mean MMTOOL [ like i tried with the sabertooth ] that can break motherboards...[ there should exist rules for microcodes , one of them being the reason why they are duplicated ] so UBU stays a dangerous tool :] . once again we fallback on the back of those that have to update BIOS...and that are really not "hard worker" ...
BIOS is the final touch of mobo and increase performances with less wastes of electricity ...
as "Coder-Rousky" aka Coderush now works to create bios , may be some new tools will come and make UBU error free .
for easy handling of bios , motherboards designers could switch to a new dual system with the use of SD*C cards for rescue/backup/updated bios .
these cards are very small , very cheap with very large size [ 30 euros for 64 Go... while bios is only 8 or 16 Mo...] , plus can be wrote on any usb port using a little adapter ...

for the bios solution of asus bios-usb-flashback , at end of video at this link : http://event.asus.com/2012/mb/USB_BIOS_Flashback_GUIDE/ the guy talks about a security ... [ the main reason why some have trouble is that entering bios is very very very hard when in mode fast..because pc is too fast.. so a lot of user change that option ..and that explains the new reboot option "re-boot to bios" of vmware or latest mainboards..]

CPU microcode updates are no big deal. And most of times we even don`t know whether we use any programs with CPU instructions fixed by those microcode updates. It is not like each update covers 50% of instructions - just one or two.

if bios does not have a microcode for a cpu.... then the mainboard does not start at all...so when UBU deletes them ... it KILLS computers...
having the latest microcode means that the cpu will function at best...
n.b. : i am not so surprised "the bios gurus" do not post here....

Zitat von grml4d im Beitrag #19

---

if bios does not have a microcode for a cpu.... then the mainboard does not start at all...so when UBU deletes them ... it KILLS computers...
having the latest microcode means that the cpu will function at best...
n.b. : i am not so surprised "the bios gurus" do not post here....

---

Zitat von Fernando im Beitrag #20

---

Zitat von grml4d im Beitrag #19

---

having the latest microcode means that the cpu will function at best...

---

The latest BIOS modules or drivers are not automatically the best, especially not for older systems.

---

Zitat von mbk1969 im Beitrag #21

---

Zitat von grml4d im Beitrag #19

---

if bios does not have a microcode for a cpu.... then the mainboard does not start at all...so when UBU deletes them ... it KILLS computers...
having the latest microcode means that the cpu will function at best...
n.b. : i am not so surprised "the bios gurus" do not post here....

---

Why do you think that mainboard will not start without microcode update? Microcode update is completely optional thing, as I understand it.. Wrong BIOS image kills computer. If UBU prepares correct BIOS image then flashing it will not kill anything.

Edit: I searched the Inet and found that only one case could be for microcode update to be mandatory - when user plugs newer stepping of CPU which is not fully compatible with motherboard (not supported yet).

Edit: Anyway, have you stated your concerns in UBU thread(s)? There you will receive attention of BIOS gurus sooner.

---

the me firmware that i flashed last year is still in the mainboard x79 despite i reflashed the bios...
i had this message :
Error 8772: Invalid usage, -allowsv switch required to update the same version firmware

i use the updater to check file and bios : same answer
Intel (R) Firmware Update Utility Version: 8.1.40.1456
Copyright (C) 2007 - 2013, Intel Corporation. All rights reserved.

FW Version: 8.1.65.1586

the meinfo output :

Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.

Intel(R) ME code versions:

BIOS Version: 4701
MEBx Version: Not available
Gbe Version: 1.3
VendorID: 8086
PCH Version: 6
FW Version: 8.1.65.1586

FW Capabilities: 0x00110440

Intel(R) Capability Licensing Service - PRESENT/ENABLED
Intel(R) Dynamic Application Loader - PRESENT/ENABLED

Cryptography Support: Disabled
Last ME reset reason: Power up
Local FWUpdate: Enabled
BIOS Config Lock: Disabled
GbE Config Lock: Disabled
Host Read Access to ME: Enabled
Host Write Access to ME: Enabled
SPI Flash ID #1: EF4017
SPI Flash ID VSCC #1: 20052005
SPI Flash BIOS VSCC: 20052005
BIOS boot State: Post Boot
OEM Id: 00000000-0000-0000-0000-000000000000
Capability Licensing Service: Enabled
OEM Tag: 0x00000000
Localized Language: Unknown
Independent Firmware Recovery: Disabled

last thing for modding : a little tool that is able to list the cpuid in a bios file : intelmicrocodelist.exe
that works with rom or cap bios
it is at : http://www.delidded.com/how-to-update-cp...r-phoenix-bios/

Hi Fernando,

First of all, I wanna say thank you for your effort build up this unique forum, providing Option ROM and upgrades that cannot be found anywhere else. Great job indeed!

However, I believe Intel C602 Chipset belongs to Intel C600 Series Chipset and equivalent to Intel X79 Express Chipset, not X99 as you answered here. X99 is equivalent to C610 Series Chipset. Please refer to these documents from Intel: https://www.intel.com/content/www/us/en/...-datasheet.html and https://www.intel.com/content/www/us/en/...-datasheet.html

Another thing is C602 requires a specific RST(e) driver, the latest one is here: https://downloadcenter.intel.com/download/25393?v=t. It is not the same as your recommendation for X79 here: Which are the "best" Intel AHCI/RAID drivers?. Could you please modify your recommendation so it could be more helpful for other users?

Thank you, and I really love this unique, amazing forum!

Hi Fernando,

Thank you for replying.

It is very interesting that I cannot find RSTe v5.1.0.1098 anywhere on Intel's website. From the link I added above, it also clearly stated that it is the latest version. No offense, and it does not mean that I do not trust you guys. I am just curious where does that new version come from, that's it.

Btw, I am willing to contribute to your benchmarking data. Would you mind give me the testing procedure that I can follow? I am build a bunch of Virtualization clusters from scratch, and trying to micro-tweak the performance.

Hi Fernando,

I am a bit confused reading your recommendations for C600/X79 chipset:
- Regarding RAID ROM: here AHCI & RAID ROM Modules I can see only Intel RSTe RAID ROM v3.8.0.1029 is primarily designed for X79, so I assumed that's the best RAID ROM for X79/C600
- Regarding RST/RSTe driver, here Which are the "best" Intel AHCI/RAID drivers? for X79 you recommended a completely different RAID driver Intel RST v11.2.0.1006 or Intel RST(e) v13.1.0.1058, while in here Intel RST/RSTe Drivers (newest: v15.7.1.1015 WHQL/v5.1.0.1098 WHQL) you clearly stated the best driver is v3.8.3.1016
- And lastly, here in this thread, you've just answered me that "Intel C600 Series Chipset SATA AHCI/RAID Controllers are supported by all currently available Intel RSTe drivers (from the v3, v4 and v5 platform) and some Intel RST(e) drivers (from the v12 and v13 platform). The currently latest Intel AHCI/RAID drivers, which do support Intel C600 Series Chipsets, are the RSTe drivers v5.1.0.1098 WHQL dated 04/20/2017."

Just to let you know that I read all your sticky threads, and they lead me to a somehow confusion :) So, could you please, based on your benchmark results, recommend me the best RAID ROM and appropriate RST/RSTe driver for C600/X79 chipset?

Thank you,