[ARCHIVE] Outdated UBU Tool related Questions, Reports and Suggestions

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

Asus990fxSabertoothRev2.0 _Modules.rar (394 KB)

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

Added:


I think this module is better not to touch it PEIM.
Compared microcode that Asus Sabertooth 990fx rev2.0 that AÛRoñk 990FX Extreme4 - identical.

@All
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.
That is why I have just updated the start post of this thread.

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.



Probably. :slight_smile:


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

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

Done!

@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.

drvver_check.rar (964 KB)

check2.rar (10.3 KB)

@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


It is no longer relevant. See post from lordkag [Tool] "UEFI BIOS Updater" (UBU) (49) 9.


I remember. But there was concern that it would be if not interchangeable.


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


FM2+ I have not looked


Forgot to remove after assembly FFS.


Is not actual, as soon as subcorrected FindVer.


Agreed. This is for myself, I added.


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


With this clear. Should be excluded.


This has let the users themselves are involved.


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.

That is a pity for users with an AMD chipset mainboard, but I can totally understand you. It is AMD themself, who makes it so difficult for AMD users to get their AMD BIOS modules up-to-date.

@ Fernando
This is not the first attempt to write a script for AMD platforms. Of course, it’s much easier if AMD would not create such freaks. In result, an it just takes a lot of time and effort. But, there is still home, work, family, and life just outside the window. :slight_smile:
I’m sorry too, but the truth is, be an ant to carry an elephant is very hard.

Hi everybody.
Great tool. I really like it :smiley:

But the AMD UEFI RAID DRIVER ver. 1.0.0.49 doesnt work on my Crosshair V.
the Legacy Rom works fine. After Flashing and enabling uefi driver in bios. i get an error message after reboot.
will post a screenshot later.
Maybe you can separate the options further. so only legacy can be updated.

The AMD Agesa works fine for me too. Does the Agesa include the µCode? (Bulldozer Conditioner says i need an update )

Thanks in advance.

@ shm0:

Welcome at Win-RAID Forum and thanks for your important feedback about the AMD support of the upcoming UBU tool v1.8.0.

Regards
Fernando


Because the module is assembled for Aptio 5. If there is a desire to be tested, then I can do for Aptio 4. And thank you so much. For confirmed that FFS assembled for Aptio 5 will not work in Aptio 4.


Wait and see. :slight_smile:


On this occasion, I hope to answer lordkag.
If possible please send screenshots and a link to your BIOS.

@ Fernando
Or maybe not so bad? :slight_smile:

My optimism rises.

Okay there are other problems too.
i cant save any bios setting. just defaults back. Dunno Why.

Here is the screenshot (not the best one uh)



And Link to my BIOS:

http://dlcdnet.asus.com/pub/ASUS/mb/Sock…a-ASUS-1703.zip

My optimism rises.



If there are screens and BIOS, then AM3 +, I think does not matter where they will be placed MISC modules in FC or FD. For EDF, rebuild modules FFS 5 minutes. :slight_smile:

@shm0


Flashing while back the original BIOS.

Message in the screenshot gives EFI RAID?

Yes thats the message with efi raid enabled.

There is a newer Version of the Motherboard Crosshair V Formula Z.
It has uefi driver 1.0.0.45. (mine has 1.0.0.17)
I modded my bios with that version maybe it works. i will report back.

// Update

Tested 1.0.0.45 also not working :expressionless: