Boards with 32MB BMC chip cannot be upgraded to BMC 4.0+. Some features (e.g. Redfish API) may not function properly in BIOS 4.01+ when paired with BMC 3.0. If you don't need advanced BMC features it should be fine to stick with 32MB BMC chip and 3.0 BMC.
You should not be uploading the zip file in BMC. You should unzip the BIOS zip and only upload the .ROM file. One drawback of not having secure BIOS is that the BIOS flash in BMC will not do any validation on the file you've uploaded. If you upload the zip it will flash using the zip with...
Just don't upgrade to BMC v4.x unless you are sure you are having a 64MB BMC chip.
Upgrading BIOS is generally safe. Even if you mess up you can always reflash as long as BMC is not dead. And this board does not have secure bios, which means you can freely downgrade or even mod the BIOS image.
Even for ASRock Rack motherboards ReBAR is not supported in public BIOS.
https://forums.servethehome.com/index.php?threads/epyc-3rd-gen-resizable-bar-support.34005/post-367121
I don’t think there are any EPYC motherboards have official ReBAR support from manufacturer…
Unfortunately Supermicro has secure BIOS starting from H12 so we cannot mod it on our own.
UPDATE: The latest BIOS version of SuperMicro H12SSL includes ReBAR support.
Looks like the new BIOS comes without a release note this time...
The only thing I noticed is for 7003, the AGESA version is updated to MilanPI-SP3 1.0.0.9.
And after upgrading the Tctl/Tdie seem to be reporting weird temperature readings on my EPYC 7543.
Before upgrade (2.4):
After upgrade...
On-die ECC is not equivalent to ECC RAM.
From my understanding, on-die ECC happens within each RAM die. It is needed because DDR5 RAMs usually have very high clock frequencies and the possibility of on-die errors is no longer negligible.
Unlike ECC, on-die ECC can not correct bit flips that...
Seems like no EPYC motherboard on market supports S3/S4 sleep states. I heard that some Xeon motherboards may support it.
Threadripper boards should support S3/S4 states though, you could put that into consideration.
Then you may be facing the same scenario as I did. Try BIOS version v4.00 and see if Remote BIOS works. If it works, then the issue is on TYAN’s side and I am afraid they currently have no plan to fix this backward compatibility issue.
Are you using BIOS version v4.01 (or newer) with BMC R3.00 (or older)?
I have consulted TYAN support and they told me newer BIOS requires BMC R4.x for full functionality. If you are stuck with old BMC due to having a 32MB BMC chip you may try file an RMA request (or consult your retailer) to...
Tyan S8030 has PCIE AER enabled by default, and does not expose option in BIOS UI to enable/disable it.
If you really want to disable it, you may try ignoring AER errors at OS level, or manually edit bits using IFRExtractor and RU.efi. The setting should lie in AMDCBS.
Disabling AER only...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.