Zitat von SoniX im Beitrag #1370

---

@sinders
Ok. Wait half an hour. Now gather FFS-files.

---

Zitat von sinders im Beitrag #1371

---

I take it this is true about the advantages of using a up to date Intel CPU Microcode?

---

@sinders
As the results?
I already have everything ready for the next test.

Zitat von SoniX im Beitrag #1374

---

@sinders
As the results?
I already have everything ready for the next test.

---

@sinders
So work?
If OROM work, then to test the EFI-files need to go to the full UEFI mode. But I think that they, too, will work without problems.

Ok. We turn to the second test. All too saioe but upgraded CPU microcode:
- 06F0 - 17
- 06F1 - 14
- 06F2 - 2D

Warning! If your motherboard does not start, then roll back to a working version.
It is waiting for the result! :)

Edit: File deleted.

Is that a fresh mod you have done with just the CPU microcode upgrade?
That would be best because it would rule out issue that may be caused with the OROM modules being changed.

This mod contains updated OROM, EFI and microcodes. It is necessary without updating the OROM and EFI?

Zitat von SoniX im Beitrag #1378

---

This mod contains updated OROM, EFI and microcodes. It is necessary without updating the OROM and EFI?

---

Ok. Only microcodes updated.

Zitat von SoniX im Beitrag #1380

---

Ok. Only microcodes updated.

---

@sinders
Stop!
Check the third test. Since FFS file microcode has 2 status! BOOT-YES and BOOT-NO. Who was stitched with the status BOOT-NO. In the original BIOS status BOOT-YES.
This can be seen by entering a command in the command line
"mmtool <BIOS file> /p". MMTool 5.00.0007.

Edit: This BOOT-YES as in original BIOS.

Sorry I don't know what you mean by Stop!.
Do you mean ok we'll stop for now?

EDIT: OK. I will test the third mod and let you know if the system still boots fine and if the microcode still seems to be working.

So, what has been done.
Taken BIOS files from Gigabyte and Asrock.
With MMTool5 been updated microcode CPU and extracted FFS-file "as is".
With UEFITool v0.20.1, was replaced two files in the BOOT-volumes.

2 finished attaching the file to X99 with different statuses BOOT.
I do not know how important this status. But I think that it is better to stick to the original.
2 status in FFS flle with microcodes.

I have tested your third mod and the system seems to boot just fine. I take it I should keep to using your third mod for the longer
testing of the updated CPU microcode since you said it is better to stick to the same as the original which is BOOT-YES?

I think it's better to stick to the original.
Thank you for tests.