@ Ozi
No, i am not working on it per se because there is nothing to do for now. What i mean is i am still always keeping a eye out to find new updates to keep this bios up to date and improve it but, like you noticed, it was very quiet on that matter in the last months and v14 is still the most up to date. Don’t worry, as soon as something new pop-up somewhere that can improve this bios, i will do a v15 as soon as that happen.
As for the Beta versions with the upgraded AGESA versions, i pretty much gave up for the time being. Nothing i tried is working perfectly without bugs and i am out of ideas for the time being on how to make this work. I am not even sure anymore if it is possible at all. At least not with my current knowledge of it. Maybe someday some new informations or knowledge will help me crack this problem open and permit me to fix this but for now, that project is all on hold and going nowhere indefinitely. All that second part to say this: Don’t expect a v15 to come out from those AGESA beta projects any time soon.
Phoenix48
And how critical are these errors? - They affect the functionality - what exactly is not functioning and is it possible to compromise with them?
List of possible bugs are:
- Memory not being reported right.
- Overclock not working.
- Cool & Quiet not working.
- System memory amount reporting glitch in Radeon settings for AMD video card.
- and maybe memory overclock not working on some versions.
- and maybe some random BSOD but i never was able to link them to it without a doubt. Maybe the bios was not responsible at that time.
Unfortunately, to know which version had which bugs with which modifications, you will have to read all the thread.
As for the question if it is possible to compromise, yes, in theory, it is sometimes possible. But, in practice, it is never truly satisfactory. At least for sure not for everyone. For example, some would never want to run their PC without Cool & Quiet even if others don’t care about that. The same thing can be said for those who always want to overclock their PC. Others are always tweaking their video cards and can’t afford to have it having some glitch infos. etc… So in that way, to please everyone, it is not really possible to compromise.
With that being said, even if i tried to update the AGESA without any glitch or bug showing, i still cant see what is the real advantage of it. For sure there must be one, no one upgrade a version just to see a new number, but there is no proof that those changes even apply to this motherboard. Remember that AMD never released a changelog (that i know of) of the AGESA versions so one can ask this question: Is it worth it to compromise for an hypothetical upgrade that no one knows what it is? Probably not. I would love to upgrade the AGESA just to be able to say that the Bios is as perfect as it can be after that but… If it is not possible then maybe it already is perfect.
Hello!
Tell me how to add a module for your M5A99X EVO board! Please manual!
MMToll - Tab Insert - CORE_DXE - 1002,4391 - Module file - Insert ?
@sazan123
To do that manually, simply follow this guide, mostly the part 5. Replace the inputs in the guide by what is needed for this ROM module: Vendor ID for AMD: 1002 and Device ID for this module: 4391
No, no need to put the AMD module in CSMCORE because it is not UEFI, you just need to put it with the other AMD PCI modules already present as option ROM (device 4392 and 4393). So you just need to do the first spoiler of part 5 in the guide and no need for the second spoiler.
If your SSD is using AHCI then yes, it will increase speed.
@Phoenix48 I do not understand this moment.
The first spoiler of the 5th part of the manual states:
Highlight the line with the CSMCORE file.
In my case, is it also worth choosing this line?
My main problem is that sleep mode does not work on Windows 1809. Does the microcode update of the CPU and AMD ACHI ROM help solve the problem?
I see what you mean… Sorry, i was not clear enough.
Both PCI and EFI module can go in the CMSCORE but it is not done by same procedure. What i should have said is yes, it goes in the CSMCORE but as a PCI module with the first procedure (first spoiler of part 5) and not as a EFI module like the second procedure (second spoiler).
@Phoenix48 Thank you very much!
Do you have any information on my problem?
My main problem is that sleep mode does not work on Windows 1809. Does the microcode update of the CPU and AMD ACHI ROM help solve the problem?
I am pretty sure that won’t help because AHCI has nothing to do with sleep mode and a microcode upgrade is doubtfull to help but, i admit, not impossible. The biggest suspect for your problem is a bug in Windows itself. If you had that problem with another Windows version then your Bios for your M5A99X EVO motherboard can be the problem but i doubt that.
@Phoenix48
The problem is only in version 1809. In Windows 10 1703, Windows 7 SP1, Linux Mint 19.1 sleep mode works fine!
On the Internet, I found a description of the same problem, with the same CPU (FX-4170), but with a different motherboard!
So this means the problem is with Windows and will be corrected with a future upgrade or, this one is less probable, that a microcode upgrade for that CPU will correct it.
@Phoenix48 Hello!
Tell me please! If I update the CPU microcodes to the latest current versions, do I need to update something else for their full operation?
@sazan123
No, the microcodes are all you need to update for them to work. But with that said, you may need to rebuild the Bios with UEFITool after the change to restore the checksum and make the Bios flashable again.
Ок, Thanks!
I updated the microcodes using the UEFITool and HxE editor manually!
I do not quite understand. Checksum must match the original bios file? Or does "checksumm" mean file integrity?
@sazan123
Sometimes, well… almost always, updating the microcodes change the checksum of the Bios so a rebuilt recalculate it and fix it so it fit the new updated Bios, otherwise most flasher will refuse to flash it and with many good reasons because this verification is made in cases, to give at least one example, that a Bios got corrupted while downloading it. A flasher usually verify the checksum before doing it and if it doesn’t find what it expect, it will refuse to do it and say something like “Checksum don’t match” or “Bios file is corrupt” or something like that. Each flasher has its own different way to say it. I am not even sure if flashback says anything at all. Maybe it just don’t do it. I don’t know.
To give an oversimplified way to explain the checksum, imagine that i wrote a program of just five letters:
ABCDE
I atribute a value to each letter: A=1, B=2, C=3, D=4, E=5
So my program has a checksum total of 15.
I update my program by replacing A with an other B.
Now i should have a checksum that says 16, but if i didn’t recalculate it, my new modded program will still show as 15 and the flasher won’t accept it.
You can also imagine that i want a bigger program that always show 25. So i invent the F character and say that this one will do nothing except take empty space to give 25. So my program has now 16 so i had 9x F to give 25.
I do another modification and add an other letter D to my program, i am now at 20 but it will show up as being too big because i am at 29 with all the F. So i must remove 4x F to compensate and restore my checksum at 25. Otherwise the flasher will see 29 and will refuse to flash it.
It is by far an oversimplification of the truth that is really going on in the Bios, and add on top of that that the Bios calculate the checksum not in decimal like i just did but instead in hexadecimal and you get a very different calculation but it is enough to show you and explain what is going on when you change something, really anything, in a Bios.
@Phoenix48 Hi! Tell me please!
After adding a module AMD AHCI ROM v3.3.2.0 for DEV_4391 discs are missing from “Bios -> Advanced -> SATA Configuration” Everywhere is displayed “Not Present”.
Although the system boots and everything works!
Google Drive IMG
Also, the speed of the SSD on my motherboard has not increased! On more advanced boards, my SSD is faster!
What am I doing wrong? How to fix?