BIOS update destroyed my KVM/vfio setup.

How do I force my x470 Taichi to revert to a previous BIOS version? It appears that it's locked down on BIOS side of things. I want to revert to 1.60 after updating to 3.20. I am experiencing the (hopefully) infamous AGESA issue that is causing my VM not to work. I *replaced* my MSI x470 Gaming Plus motherboard with this Taichi motherboard because I bricked my MSI board trying to force the BIOS to revert on it for the same problem, then I was stupid enough to think the same issue would not occur on Asrock if I updated. I guess it has to do with AGESA 0.0.7.2 . Needless to say I'm really upset. I was finally able to get the VM to boot with [URL=https://clbin.com/GGnxm]this kernel hack[/URL] but it only boots once per host boot, and the performance is really bad. I don't want to brick my Taichi like I did my Gaming Plus, can someone *please* give me instructions for a workaround of this BIOS revert lockdown? It's truly unbelievable to me that all these companies would decide to force their users in this manner. I switched to AMD from Intel *just for the cores to power this KVM/vfio setup*.

As you've discovered with your MSI, major AGESA updates, 1.0.x to 0.0.x ComboAM4, cannot be back-flashed.

Also, it is not the MB manuf's that req this, but AMD.

Apparently all the different motherboards (x470 vs x370, msi vs taichi) use different flags with their flashtools. Also I am told I have to flash down in steps (a later version, then an earlier, then an earlier). I am hoping to get explicit directions for this particular board because it's really easy to mess up. I was told that the last time AGESA had this problem it took over a year to fix...I think it's really really unfair that this BIOS update can't be reverted through normal means. Manufacturers should at least have official instructions for people who *really need* to go back to a different version. I understand it's AMD's policy to disallow updates because of people bricking their boards when they upgrade their CPUs...but come on at least give instructions or a workaround to people who are aware of that fact.

OK.

First, prior to flashing 5.30 that has 0.0.72 for my Killer SLI/ac I Disabled Fast Boot and Secure Boot in BIOS and disabled "Turn on fast startup" in Windows CP. The 'Turn on fast start' I suspect may be causing issues that are being reported here and elsewhere. Remember, the BIOS and Windows are now inextricably linked and do communicate between themselves. Disabling any cache that speeds up Windows is not a bonus when flashing a BIOS.

Into BIOS and select the Instant Flash Util and up-flashed to 5.30(0.0.72)

All is well up to this point. No sluggishness. Loads fast as ever has. I'll do some peeking under the hood before I attempt to revert back to 5.10(1.0.0.6). See where my mem in my sig will top out at as I didn't do any pre-flash benchs to compare. My mem, those G.Skill Trident-Z 4133's, I know inside out and upside down.

More to come ..............






Edited by wardog - 13 May 2019 at 2:26pm

Oops.

Let's hope I can recover it.