The RyzenSMU module returns STATUS_NOT_SUPPORTED on AMD Ryzen Z2 Extreme because model 0x24 is not recognized in
get_code_name().
CPU Information
Family: 0x1A (26 decimal)
Model: 0x24 (36 decimal)
Name: AMD Ryzen Z2 Extreme
Device: Lenovo Legion Go 2
Current get_code_name() for Family 0x1A
case 0x1A20: return CPU_StrixPoint;
case 0x1A44: return CPU_GraniteRidge;
case 0x1A60: return CPU_KrackanPoint;
case 0x1A68: return CPU_KrackanPoint2;
case 0x1A70: return CPU_StrixHalo;
// 0x1A24 is missing!
Suggested Fix
Based on the model number proximity to StrixPoint (0x20 vs 0x24), appears to be a Strix Point variant. The
fix would be:
case 0x1A20, 0x1A24:
return CPU_StrixPoint;
This would use the same SMU configuration as StrixPoint:
- Address index: 2 (cmd=0x3B10A20, rsp=0x3B10A80, args=0x3B10A88)
- PM table version msg: 0x06
- Transfer to DRAM msg: 0x65 with arg 3
- Get PM table base msg: 0x66 with args 1, 1
The RyzenSMU module returns STATUS_NOT_SUPPORTED on AMD Ryzen Z2 Extreme because model 0x24 is not recognized in
get_code_name().
CPU Information
Family: 0x1A (26 decimal)
Model: 0x24 (36 decimal)
Name: AMD Ryzen Z2 Extreme
Device: Lenovo Legion Go 2
Current get_code_name() for Family 0x1A
case 0x1A20: return CPU_StrixPoint;
case 0x1A44: return CPU_GraniteRidge;
case 0x1A60: return CPU_KrackanPoint;
case 0x1A68: return CPU_KrackanPoint2;
case 0x1A70: return CPU_StrixHalo;
// 0x1A24 is missing!
Suggested Fix
Based on the model number proximity to StrixPoint (0x20 vs 0x24), appears to be a Strix Point variant. The
fix would be:
case 0x1A20, 0x1A24:
return CPU_StrixPoint;
This would use the same SMU configuration as StrixPoint: