1. Only 439x

2. http://www.asrock.com/mb/index.asp?s=AM3%2b

I hope to help you

add: 2. but the latest agesa driver from asrock for 990fx is only version 1.2.9.0

Well, then AGESA, I will add later.
But I'm interested in this one module GUID DE3E049C-A218-4891-8658-5FC0FA84C788. It is needed or not? When you manually updated AGESA module, the change also that module?

I'm not sure, it's a question such as other modules (CpuPei, AmdInitPostPeim, AmiAgesaDxe ...)

I am also in search

Zitat von kgbab im Beitrag #727

---

I'm not sure, it's a question such as other modules (CpuPei, AmdInitPostPeim, AmiAgesaDxe ...)

---

From Asus Sabertooth 990fx rev2.0 similar to my motherboard ASRock 990FX Extreme4 with version modules 1.2.9.0

AmdAgesaDxeDriver GUID 6950AFFF-6EE3-11DD-AD8B-0800200C9A66 : ver. 1.5.0.2

AmdProcessorInitPeim GUID DE3E049C-A218-4891-8658-5FC0FA84C788 : ver. 1.5.0.2

The two modules have the same version 1.5.0.2

UBU v1.8.0 RC2
Added AGESA fpr AM3+ v1.5.0.2

Added:

Zitat von kgbab im Beitrag #729

---

AmdProcessorInitPeim GUID DE3E049C-A218-4891-8658-5FC0FA84C788

---

@All
Who has the results of the work of update modules AMD SATA and AGESA?

Zitat von Fernando im Beitrag #732

---

Zitat von SoniX im Beitrag #731

---

Who has the results of the work of update modules AMD SATA and AGESA?

---

Maybe some users with an actual AMD chipset system have not even realized, that there is an UBU tool version available, which does support the modding of their UEFI BIOS.

---

Zitat

---

That is why I have just updated the start post of this thread.

---

Thank you. I thought the first post hardly anyone reads, usually just download, and then start to get questions. :)

By the way, add another:
Added OROM AMD AHCI 4391 - v3.2.1.0
Added OROM AMD RAID+MISC 4392-4393 and 7802-7803 - v3.3.1540.19
Added EFI RAID and Setup - v1.0.0.49
Update DrvVer to v0.11.1

@SoniX

1. SABERTOOTH-990FX-R20-ASUS-2501 is a good example where ...FC and ...FD are reversed. In this example 1002-4392 is in ...FD.ffs and 1002-4393 is in ...FC.ffs. So you need that whole check I told you in previous message. Or this might only happen in Asus BIOS, so you only check if it is Asus.

2. Something that I also needed to correct: MISC.SIG is the signature, MISC.BIN is the actual name.

3. MISC.BIN 3.3.1540.19 is already compressed, second compression in ffs gains nothing, but adds extra (small) time and invites trouble. I was saying to leave the inner misc.bin as it is, not the whole ffs. Extract uncompressed with MMTool and use as is.

4. There are 4 (!) AMD EFI RAID drivers, as you can see in the package uploaded by kgbab. You should add SCSIBus and SCSIDisk to the list. There are also RAIDXpert2-F10, RAIDXpert2-F50 for FM2+ boards.

5. What is the purpose of 4392m.bin, 4393m.bin, 7802m.bin, 7803m.bin? I doubt you will find MISC.BIN outside ffs in UEFI.

6. It might be easier to replace "if exist temp\xxxx.tmp echo %vermxxxx%" with "if defined vermxxxx echo %vermxxxx%".

7. Using findver to extract AMD name for VBIOS is tricky, because that is the codename, not the actual name of the VBIOS. See in file drvver_check.rar attached.

8. There are some glitches with drvver in some older AMD RAID Utility and newer AMD GOP. See file attached.

9. Don't add AGESA to UBU, as it is BIOS dependent. If you will check, you will see that it is different even between BIOS number upgrades for the same board, because it is compiled, not inserted. And it might also add some code in FchDxe, FchSmmInit, AmdProcessorInitPeim. Only someone from inside could tell.

10. AMD microcodes could be added with UEFIPatch at some latter date, if it would allow [begin pattern + random filling bytes = size] be replaced by a file.

Could you also check the other file attached and see if it is useful? It was based on RC1, as it makes no sense in using RC2.

@SoniX
The latest motherboard am3+ is the MSI 970 gaming
http://www.msi.com/support/mb/970_GAMING.html#down-bios
The agesa version is 1.5.0.5

Zitat von asrlab im Beitrag #736

---

@SoniX
The latest motherboard am3+ is the MSI 970 gaming
http://www.msi.com/support/mb/970_GAMING.html#down-bios
The agesa version is 1.5.0.5

---

Zitat von lordkag im Beitrag #735

---

@SoniX

1. SABERTOOTH-990FX-R20-ASUS-2501 is a good example where ...FC and ...FD are reversed. In this example 1002-4392 is in ...FD.ffs and 1002-4393 is in ...FC.ffs. So you need that whole check I told you in previous message. Or this might only happen in Asus BIOS, so you only check if it is Asus.

---

Zitat

---

2. Something that I also needed to correct: MISC.SIG is the signature, MISC.BIN is the actual name.

3. MISC.BIN 3.3.1540.19 is already compressed, second compression in ffs gains nothing, but adds extra (small) time and invites trouble. I was saying to leave the inner misc.bin as it is, not the whole ffs. Extract uncompressed with MMTool and use as is.

---

Hmm .. It's not so simple. :(
By the way, I do not use MMTool for assembly FFS, only EDK2 and UEFITool.

Zitat

---

4. There are 4 (!) AMD EFI RAID drivers, as you can see in the package uploaded by kgbab. You should add SCSIBus and SCSIDisk to the list. There are also RAIDXpert2-F10, RAIDXpert2-F50 for FM2+ boards.

---

FM2+ I have not looked

Zitat

---

5. What is the purpose of 4392m.bin, 4393m.bin, 7802m.bin, 7803m.bin? I doubt you will find MISC.BIN outside ffs in UEFI.

---

Forgot to remove after assembly FFS.

Zitat

---

6. It might be easier to replace "if exist temp\xxxx.tmp echo %vermxxxx%" with "if defined vermxxxx echo %vermxxxx%".

---

Is not actual, as soon as subcorrected FindVer.

Zitat

---

7. Using findver to extract AMD name for VBIOS is tricky, because that is the codename, not the actual name of the VBIOS. See in file drvver_check.rar attached.

---

Agreed. This is for myself, I added.

Zitat

---

8. There are some glitches with drvver in some older AMD RAID Utility and newer AMD GOP. See file attached.

---

know, then we'll fix it. Thanks for the archive collection is on what is now checking work DrvVer.

Zitat

---

9. Don't add AGESA to UBU, as it is BIOS dependent. If you will check, you will see that it is different even between BIOS number upgrades for the same board, because it is compiled, not inserted. And it might also add some code in FchDxe, FchSmmInit, AmdProcessorInitPeim. Only someone from inside could tell.

---

With this clear. Should be excluded.

Zitat

---

10. AMD microcodes could be added with UEFIPatch at some latter date, if it would allow [begin pattern + random filling bytes = size] be replaced by a file.

---

This has let the users themselves are involved.

Zitat

---

Could you also check the other file attached and see if it is useful? It was based on RC1, as it makes no sense in using RC2.

---

If not difficult to do in RC2. And that code so that you can already get confused.

Add from myself. So I did not want to support updates for AMD platforms. So most likely, once again I give up trying to write support, upgrade modules for AMD.
In the release version 1.8.0 will display only some versions.
So please accept my apology.