ASUS RAMPAGE III EXTREME BIOS - V1601 - Updated OROM MOD

[weingeist]

i have a i7-980X, thats very great

[JoernGerken]

I am now suspecting that VT-d was causing booting issues long ago before Win10 1803 but not as critical. I also suspect that there may be a glitch with one of the updated modules of our modded BIOS (probably inhered from ZioMod).

My search for a new 06C2 microcode led me here. It is MCU 0x1E.
Maybe pir8man would want to create a new BIOS for testing.insp

There are similar problems with VT-d "enabled", when Windows 7 comes out. Maybe the marvell updates (in the past) are responsible for VT-d "enabled" booting issues, but I'm not able to figure that out and I don't need direct I/O for my virtual machines.

I take s19i from page 1, download the microcode from the link above and followed the steps provided here to integrate the microcode updates, flashed the bios, load the Setup Defaults, disable JMicron, SATA6G and 1394, check, that VT-d is disabled, boot Windows 10 17134.48, don't install KB4100347 (!Important) and got my system Meltdown and Spectre protected; have a look at the attachment.

Thanx Stahab for pointing me to the (old) VT-d issue and a very special Thank You to pir8man for your BIOS-mods.

[rattyto]

i have a i7-980X, thats very great

I have the same CPU. Which BIOS Ver. have you installed? What happens if you enable BOOT on LAN in the BIOS?

Do you receive the same error message for the PXE and Vendor ID as me?

Thanks.

[weingeist]

Bios S91i Yes i have the same error. The JMircon has no Bios Text.

[weingeist]

Here is the S19i-Final.rom inklusive the HP Microcode for i7-980X

[pir8man]

Hello, i have install the S19t_Final BIOS Version and if i enable the Boot on LAN Option in BIOS then i receive the error message : "PXE-E01 PCI Vendor and Device IDs do not match!" what is wrong in my doing? I have try other versions and the error message is the same.

Another Question: Is it normal with this Version not seeing the JMicron boot text?

I can roll out some test BIOS's with older NIC OROMs.  I never use that feature, so I never came across it in my testing.


For others facing the VT-d compatibility issue.  There is nothing I can do to update the BIOS code itself to improve compatibility.  Our 1601 BETA bios only had memory compatibility updates over the 1502 (last official) BIOS. Unfortunately there was no update to the VT-d compatibility from ASUS for the R3E. I will roll out some new S20 releases with the latest (04/2018) CPU Microcode update.  Hopefully that will have an impact.

I do not modify our BIOS or the OROMs. I only replace the existing OROMS with the updated ones.  Zio did the same, I just follow his instructions for my work here.  Any bugs that ZIO or myself introduce would be limited to the device the updated OROM is runnning, or from the CPU microcode updates.  I can always roll back if I am introducing new problems with an OROM.

I'll have the latest microcode updates available for testing in a day (or less).

[weingeist]

very nice pir8man and very great work

[pir8man]

ok, Here is the S20 TEST BIOS release.  I combined each version in one archive.  Just read Post #1 to get the file specific details.

Only thing updated here is CPU Microcodes.

Updated Microcodes:
206C2 Revision 1E (2018-01-23) - Supported CPU's:
Intel® Core™ i7-970, 980
Intel® Core™ Processor Extreme Edition i7-980X, 990X
Intel® Xeon® Processor W3670, W3680, W3690
Intel® Xeon® Processor X5650, X5660, X5670, X5680, X5690


106A4 Revision 13 (2015-06-30) - Supported CPU's:
Intel® Core™ Processor Extreme Edition i7-975
Intel® Core™ Processor i7-920, 930, 950, 960 


106A5 Revision 19 (2013-06-21) - Supported CPU's:
Intel® Core™ Processor Extreme Edition i7-965
Intel® Core™ Processor i7-920, 940 106A5 03 Stopped 0x1B --- ---
Bloomfield Xeon Intel® Xeon® Processor W3520, W3530, W3540, W3550,
W3565, W3570, W3580 
Intel® Xeon® Processor W5580, W5590
Intel® Xeon® Processor X5550, X5560, X5570

NOTES:
I did a bit of hunting to make sure I had the latest microcodes available. I found that only 206C2 was updated this year for the latest spectre/meltdown issue. I updated the other two pertinent modules for the lower-end processors to newer revisions, but they are not upadated/patched for spectre/meltdown bugs.
Supposedly, there is an update for 106A5 from this year (2018-01-24), but the two copies I found of this were not readable/injectable.  Intel did not release this update and it is not available from their website.  I assume it is mislabeled or just poorly extracted.  Either way, we have to wait for a working version.

EDIT:  See post #110 for TEST2 file.

[calestrom]

ok, Here is the S20 TEST BIOS release.  I combined each version in one archive.  Just read Post #1 to get the file specific details.

Thanks for the bios update pir8man. All seems to be working ok. Spectre and Meltdown are protected according to InSpectre.
I'm using the raid-0 and the trim function seems to be working just fine.

[pir8man]

I found a working export of 106A5 microcode.  One of the original sites I was searching (Microcode repo) updated their copy and it does import correctly now.  Details:

106A5 Revision 1D (2018-05-11) - Supported CPU's:
Intel Core Processor Extreme Edition i7-965
Intel Core Processor i7-920, 940 106A5 03 Stopped 0x1B --- ---
Bloomfield Xeon Intel Xeon Processor W3520, W3530, W3540, W3550,
W3565, W3570, W3580
Intel Xeon Processor W5580, W5590
Intel Xeon Processor X5550, X5560, X5570


Interestingly, they also had another 206C2 microcode update, with revision 1F with a date of 2018-05-08.  However this copy was not injectable to our BIOS.  As calestrom already tested the 206C2-1E patch and it has meltdown/spectre bug fixed.  This 1F patch may be unnecessary.  nontheless, I will monitor for a fixed 1F patch for us.

SEE OP for S20 Final