-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Zen3 / Ryzen 5000 #9
Comments
Perhaps it's because of the older version. My current version is 1.3.4, but I haven't released it. |
Other possibility is the latest bios for your board removed the "read" command. The mailbox scanning function does not work properly from some time with the new AGESA updates rolled out to vendors. Here's a fresh build from yesterday if you're not afraid to try. |
I've built a version yesterday from the current master, trying out your version now, but there doesn't seem to be much of a difference between these two. The debug report now shows the mailboxes correctly, and it also doesn't seem to crash anymore while monitoring the mailboxes. I hadn't actually tried this with the current 1.3.2 release, because I thought it was broken altogether. {
"AppVersion": "1.3.4.0",
"OSVersion": "Microsoft Windows 10 Enterprise LTSC",
"CpuName": "AMD Ryzen 9 5900X 12-Core Processor",
"CodeName": "Vermeer",
"CpuId": "00A20F10",
"Model": 33,
"ExtendedModel": 32,
"PackageType": "AM4 (2)",
"FusedCoreCount": 12,
"PhysicalCoreCount": 16,
"NodesPerProcessor": 1,
"Threads": 24,
"SMT": true,
"CCDCount": 2,
"CCXCount": 2,
"NumCoresInCCX": 6,
"MbVendor": "Micro-Star International Co., Ltd.",
"MbName": "MAG X570 TOMAHAWK WIFI (MS-7C84)",
"BiosVersion": "1.50",
"SmuVersion": "56.44.0",
"SmuTableVersion": 3672068,
"PatchLevel": "0A201009",
"Mailboxes": [
{
"MsgAddress": "0x03B10524",
"RspAddress": "0x03B10570",
"ArgAddress": "0x03B10A40"
},
{
"MsgAddress": "0x03B10528",
"RspAddress": "0x03B10574",
"ArgAddress": "0x03B10A60"
},
{
"MsgAddress": "0x03B1052C",
"RspAddress": "0x03B10578",
"ArgAddress": "0x03B10A80"
},
{
"MsgAddress": "0x03B10530",
"RspAddress": "0x03B1057C",
"ArgAddress": "0x03B109C4"
},
{
"MsgAddress": "0x03B10534",
"RspAddress": "0x03B10980",
"ArgAddress": "0x03B109E0"
}
]
} |
If I remember correctly, the GET command was not working for Vermeer. This is the MP1 command ID to get the margin, leaving the argument to the default 0 should return it for the first core.
If that doesn't work, then there might be another method, but I have no access to a Vermeer system right now. PS: You can see discovered commands in the Core project For example, specific Zen3 commands that extend the Zen2 set of commands: You can also use the rest of the Zen2 commands in addition to the specific Zen3 commands: HSMP commands: |
So it's what I remember - command for getting the CO value for a core is not available. |
So I guess it was 0x3B, 0x3C and/or 0x3D, which define the TDC, EDC and PPT power limits. Calling them with 0 does set the limit to 0, forcing the CPU into a low power stage. Is there some safe way to test these addresses without risking to permanently damaging the processor? Some other maybe interesting results, I did stop at that point. 0x3A with arg 0 returns:
0x39 with arg 0 returns:
The original max CPU frequency? 0x38 with arg 0 returns:
|
I haven't managed to kill/damage a retail SKU, but I'd still advise against trying unknown commands. |
And another FYI, I updated the BIOS now, which includes AGESA ComboAM4v2PI 1.2.0.A, and the PBO tab now correctly displays the CO values from the BIOS. The 0x48 also returns a value. {
"AppVersion": "1.3.4.0",
"OSVersion": "Microsoft Windows 10 Enterprise LTSC",
"CpuName": "AMD Ryzen 9 5900X 12-Core Processor",
"CodeName": "Vermeer",
"CpuId": "00A20F10",
"Model": 33,
"ExtendedModel": 32,
"PackageType": "AM4 (2)",
"FusedCoreCount": 12,
"PhysicalCoreCount": 16,
"NodesPerProcessor": 1,
"Threads": 24,
"SMT": true,
"CCDCount": 2,
"CCXCount": 2,
"NumCoresInCCX": 6,
"MbVendor": "Micro-Star International Co., Ltd.",
"MbName": "MAG X570 TOMAHAWK WIFI (MS-7C84)",
"BiosVersion": "1.D0",
"SmuVersion": "56.76.0",
"SmuTableVersion": 3672069,
"PatchLevel": "0A201025",
"Mailboxes": [
{
"MsgAddress": "0x03B10524",
"RspAddress": "0x03B10570",
"ArgAddress": "0x03B10A40"
},
{
"MsgAddress": "0x03B10528",
"RspAddress": "0x03B10574",
"ArgAddress": "0x03B10A60"
},
{
"MsgAddress": "0x03B1052C",
"RspAddress": "0x03B10578",
"ArgAddress": "0x03B10A80"
},
{
"MsgAddress": "0x03B10530",
"RspAddress": "0x03B1057C",
"ArgAddress": "0x03B109C4"
},
{
"MsgAddress": "0x03B10534",
"RspAddress": "0x03B10980",
"ArgAddress": "0x03B109E0"
}
]
} |
Thanks for confirming the command is available in newer bioses. |
Does this support Ryzen 5000 CPUs?
I'm getting mixed results, the CPU is correctly detected, but the PBO values are all 0, despite being set in the BIOS.
The SMU send message also sometimes fails, then I have to do one or multiple rescans to make the 0x1 test message work again.
And the Debug Report does not show any mailboxes, even if the scan process succeeded before.
It also crashes after a while when I open the SMU monitor after a scan. It displays a couple of messages and then closes without an error.
The text was updated successfully, but these errors were encountered: