Zitat von Fernando im Beitrag #4111

---

Can you help?

---

Do we have an idea when feature parity will be reached with v1.70 to v1.69?

While this is great for some newer boards, its BLOODY MAGIC for older ones, AMD specifically, and the only thing I was able to update with my AMD board is the Killer, none of the rest of the AMD rom was able to be updated (storage, my main concern).

As of now, I have to run it through v1.69, first, then v1.70

I tried new option M1 from ubu b12 to update MSI X299 bios - new microcode was added in a new "Vol 1" but the old microcode was also left in the bios in the original "Vol 4". :

╔═══════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟─┬─────┬────────────────┬────────┬──────────┬────┬───────┬────────┬────╢
║#│CPUID│ Platform ID │Revision│ Date │Type│ Size │ Offset │Last║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║1│50654│B7 (0,1,2,4,5,7)│200004D │2018-05-15│PRD │ 0x7C00│0x7F23F8│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║2│50652│ 97 (0,1,2,4,7) │80000037│2017-05-02│PRE │ 0x7400│0x7F9FF8│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║3│906E9│ 2A (1,3,5) │ 8E │2018-03-24│PRD │0x18000│0x8013F8│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║4│506E8│ 22 (1,5) │ 34 │2016-07-10│PRD │0x17800│0x8193F8│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║5│50654│B7 (0,1,2,4,5,7)│2000043 │2018-01-26│PRD │ 0x7000│0xD00090│ No ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║6│506E8│ 22 (1,5) │ 34 │2016-07-10│PRD │0x17800│0xD07090│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║7│906E9│ 2A (1,3,5) │ 84 │2018-01-21│PRD │0x18000│0xD1E890│ No ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼────────┼────╢
║8│50652│ 97 (0,1,2,4,7) │80000037│2017-05-02│PRE │ 0x7400│0xD36890│Yes ║
╚═╧═════╧════════════════╧════════╧══════════╧════╧═══════╧════════╧════╝
Microcodes GUID 17088572-377F-44EF-8F4E-B09FFF46A070

I was able to manually delete the old microcode from "Vol. 4" using MMTOOL, leaving only the new microcode, but I have not tried flashing it yet. I will flashing it if you think it's probably correct (all microcode in new Vol. 1, all old microcode in Vol. 4 deleted.)

╔══════════════════════════════════════════════════════════════════════╗
║ Intel ║
╟─┬─────┬────────────────┬────────┬──────────┬────┬───────┬───────┬────╢
║#│CPUID│ Platform ID │Revision│ Date │Type│ Size │ Offset│Last║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼───────┼────╢
║1│50654│B7 (0,1,2,4,5,7)│200004D │2018-05-15│PRD │ 0x7C00│ 0x18 │Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼───────┼────╢
║2│50652│ 97 (0,1,2,4,7) │80000037│2017-05-02│PRE │ 0x7400│ 0x7C18│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼───────┼────╢
║3│906E9│ 2A (1,3,5) │ 8E │2018-03-24│PRD │0x18000│ 0xF018│Yes ║
╟─┼─────┼────────────────┼────────┼──────────┼────┼───────┼───────┼────╢
║4│506E8│ 22 (1,5) │ 34 │2016-07-10│PRD │0x17800│0x27018│Yes ║
╚═╧═════╧════════════════╧════════╧══════════╧════╧═══════╧═══════╧════╝

@Net7
Do you have a motherboard for AMD?
If the Aptio 4 platform, then use 1.69 to upgrade the RAID.
If the platform Aptio V, then send a link to the BIOS.

Zitat von SoniX im Beitrag #4115

---

@Net7
Do you have a motherboard for AMD?
If the Aptio 4 platform, then use 1.69 to upgrade the RAID.
If the platform Aptio V, then send a link to the BIOS.

---

@lettermand99
It's strange. All microcodes must be removed from the 4th volume, and new ones are added to the 1st volume.
s there something wrong. Send your BIOS.

@Net7
I did not quite understand. And what exactly you can not update?

Version 1.70 in the beta stage. In the near future, will be added support for AMD on the platform Aptio V.
For the Aptio 4 platform, I'll add gradually.

When I see that editing manually, I always update both volumes with matching code. I'm not sure if that is correct thing to do, or if even necessary, but BIOS works when doing that way.
Does it also work as a standard editing method to only put new in single volume and remove all from any secondary volume?

@Lost_N_BIOS
It is impossible to say unambiguously which method will be working. Everything should be tested.

NEW! Linux* Processor Microcode Data File dated 03-July-2018 released!

- Update to 20180703 release, fixes CVE-2018-3640 (Spectre v3a) CVE-2018-3639 (Spectre v4).

https://downloadcenter.intel.com/downloa...e-Data-File?v=t


-- Updates upon 25-April-2018 release --

---- updated platforms ------------------------------------

SNB-EP C1 6-2d-6/6d 0000061c --> 0000061d Xeon E5
SNB-EP C2 6-2d-7/6d 00000713 --> 00000714 Xeon E5
IVT C0 6-3e-4/ed 0000042c --> 0000042d Xeon E5 v2; Core i7-4960X/4930K/4820K
IVT D1 6-3e-7/ed 00000713 --> 00000714 Xeon E5 v2
HSX-E/EP/4S C0 6-3f-2/6f 0000003c --> 0000003d Xeon E5 v3
HSX-EX E0 6-3f-4/80 00000011 --> 00000012 Xeon E7 v3
SKX-SP/D/W/X H0 6-55-4/b7 02000043 --> 0200004d Xeon Bronze 31xx, Silver 41xx, Gold 51xx/61xx Platinum 81xx, D/W-21xx; Core i9-7xxxX
BDX-DE A1 6-56-5/10 0e000009 --> 0e00000a Xeon D-15x3N

---- intel-ucode-with-caveats/ ---------------------------- *

BDX-ML B/M/R0 6-4f-1/ef 0b00002c --> 0b00002e Xeon E5/E7 v4; Core i7-69xx/68xx

* -- intel-ucode-with-caveats/ --
This directory holds microcode that might need special handling. BDX-ML microcode is provided in directory, because it need special commits in the Linux kernel, otherwise, updating it might result in unexpected system behavior. OS vendors must ensure that the late loader patches (provided in linux-kernel-patches\) are included in the distribution before packaging the BDX-ML microcode for late-loading.


NEW! Intel Microcode Update Guidance pdf also released!

https://www.intel.com/content/dam/www/pu...te-guidance.pdf

For Skylake-X, the 4D microcode increases the TJMax by 5°C (105 to 110°C) and therefore the core temperatures too.
So I stay with the 49

@SoniX
When trying Dev15 version to mod the new v3902 BIOS of SabertoothX99 I get a UBU crash with Network Option and any others.
The UBU tool does close abruptly (black screen does disappear).


When trying Dev12 version for the same scenario ALL the options are working well:

@100PIER
Fixed. Re-Upload.

@Sonix
Yes, Dev15_fix version fixed all the problems except the Network Intel update.
Look at Dev12 test screens I had reported, modding Intel Lan is working well.
Look at Dev15_fix test screens herebelow, modding Intel Lan is not working properly (update not accepted)
However, Realtek Lan uupdates are properly working:

@100PIER
b16