Shugs ? My Taichi is not having any issues everything works as it should. Might change once Navi releases.
Why? It’s pretty common for enterprise hardware, vendors often have these supported/recommended upgrade chains/paths, I know it’s a bit unusual for consumer hardware, but calling it alarming is an overreaction.
I would say that is rma. I would normally say driver issues but the nic not working is not good. Not all hardware monitoring software always compatible with the lastest and greatest sometimes.
Anyhow, I’m not here to discuss the subtleties of the English language. So take it as you will.
The codeblock in the Firmware performing the update flash has changed in crucial ways between these versions.
These changes are not insignificant. It can not be guaranteed that it wont set your house on fire. Yet none of the Vendors seem to be treating this firmware update release with the care and attention it requires.
(Seems that the vega disappearance issue is due to an issue with gpu i2c (vrm) monitoring, and unrelated: https://www.hwinfo.com/forum/Thread-IMPORTANT-HWinfo-Vega-64-intermittent-crash )
2 Likes
This one should have working pstates, and I would like to be brave but no Taichi 
Also, HWiNFO64 just got update
Fixed reporting of temperatures on AMD Vega since Crimson 17.11.2 driver.
GPU I2C support is now automatically disabled on AMD Vega series to prevent a possible system crash.
Automatic disabling of GPU I2C support can be circumvented using a new GPU I2C Support Force option.
1 Like
I’m still interested/impressed in how the driver team managed to break something as standard as i2c.
excellent job…
Quite. Though I’m mostly just reassured to know that it’s unrelated to the bios update, or presaging a board issue.
As for RMA-ing: I guess I should, but losing access to my PC for the duration isn’t appealing.
I’m almost certain that this option doesn’t do what everyone thinks it does.
https://www.phoronix.com/scan.php?page=news_item&px=AMD-PSP-Disable-Option
https://drive.google.com/file/d/1b4p3d-gtHbFvkUbHYC8HSIviL-1ssC7V/view
1 Like
i2c allows for basically everything. And without an oscilloscope and Vega in hand, this is a black box.
When i got my new box last month i updated to latest bios which was September, count me as one of those that probably wont update unless i have too. It works and its not intel so as long as i dont get zen+ or zen2 i shouls be fine.
I updated my Prime X370 Pro to 3203 and subsequently 3401 and have had no major issues beyond the 3203 BIOS breaking compatibility with a cheapo wifi card (which I returned). Granted it took some troubleshooting to figure that one out, but otherwise system itself is fine.
The bigger issue I had was not being able to roll back to 1201.
1 Like
Thanks for the warning. However, I prefer to wait on new BIOSes anyway 
That being said, a new BIOS isn’t available for my Taichi yet.
I’m currently poking at the two latest Firmware files for my ASRock X370 Gaming K4 board.
The major thing I’ve noticed is that a volume image responsible for CSM (Legacy Boot & Devices on UEFI) has been removed in BIOS version 4.10 versus 3.40
On the right we have Firmware 3.4 and on the Left 4.10
Notice the 5C3DB34C-75BE-4641-B064-C6247ABE1FF6 File that’s present in 3.40 but not in 4.10
It contains a few DXE (Driver Execution Environment) Files.
Let’s see if they’ve been moved to elsewhere in the file structure.
EDIT:
Ok so the CsmDxe File has been merged into a different part of the volume image, same GUID. It’s also smaller.
It appears that LegacyInterrupt, LegacyRegion and CsmVideo have been removed or likely rolled into one of the other modules. I’ll have a more complete analysis once I’ve redesigned my tools to handle this AMD Firmware better. 
Ps Lots of interesting PSP related code 
9 Likes
That’s why I love this form, normal people don’t do this. (I mean this as a compliment )
Edit: Apparently ASRock has removed the BIOS from it’s page.
@catsay Shouldn’t this be AGESA 1.0.0.7, or did I get something wrong?
5 Likes
Technically yes It should be Agesa 1.0.0.7. But that got vetod since this BIOS is a major release, rather than a minor increment as the previous ones where.
Hence why ASRock is also using v4.10 instead of v3.50 on my mainboard as the version designator.
1 Like
Thanks for clarifying that,
I’m sort of having to relearn how UEFI and PEIM / PPI interfaces all work.
Thankfully though all the Driver files inside UEFI are PE (Portable Executable) Format. Or Terse Executable format. Same as Microsoft uses. 
This slide and presentation where really helpful in me getting started.
Only difference was adapting the tools to work around the AMD Differences compared to Intel.
For example the Management Engine block in the Firmware structure isn’t then used for the equivalent ARM PSP code. It’s laid out somewhat differently and the Headers for some blocks of firmware aren’t known yet so I’m treating them as data padding.
If I can finally get a proper SPI Flash Rom clipper I might try and read the Firmware directly out of the flash rom on a mainboard.
It seems the flashing process decodes part of the firmware before writing it to the chip.
4 Likes
The AGESA 1.0.7.2 helped my system reach spd and rated ram speed. I read about it being warned about bugs but… if you are not getting the spd to work properly prior… you will try out the new bios anyhow.