Support request: Zen 5 “Strix Halo” (CPUID 0x00B70F00, family 0x1A model 0x70) — ryzen_smu fails to initialize #27
Description
Support request: Zen 5 “Strix Halo” (CPUID 0x00B70F00, family 0x1A model 0x70) — ryzen_smu fails to initialize
AMD Ryzen™ Al Max+ 395
Summary
On a Zen 5 “Strix Halo” system, ryzen_smu v0.1.7 loads but fails to initialize, so no /sys/kernel/ryzen_smu_drv is created. RyzenAdj therefore falls back to /dev/mem. dmesg shows the CPU is recognized as family 0x1A, model 0x70 but reported as “Unknown Zen5/6 processor model”.
I can set Curve Optimizer under Windows (UXTU), so firmware is not hard‑locked. I’m happy to test patches/branches.
Environment
CPU/APU: AMD Zen 5, identified by RyzenAdj as “CPU Family: Strix Halo” - AMD Ryzen™ Al Max+ 395
CPUID: family 0x1A, model 0x70, stepping 0x0 (0x00B70F00)
OS: Arch Linux (rolling)
Kernel: 6.16.2-2-cachyos-lto
ryzen_smu: v0.1.7 (DKMS)
RyzenAdj: v0.17.0
What happens
Module loads, but initialization fails and the sysfs interface is missing.
RyzenAdj reports no compatible ryzen_smu and falls back to /dev/mem.
Logs
dmesg excerpt:
ryzen_smu: loading out-of-tree module taints kernel.
ryzen_smu: module verification failed: signature and/or required key missing - tainting kernel
ryzen_smu: loading version: 0.1.7
ryzen_smu: CPUID: family 0x1A, model 0x70, stepping 0x0, package 0x1
ryzen_smu: CPUID: Unknown Zen5/6 processor model: 0x70 (CPUID: 0x00B70F00)
ryzen_smu: Failed to initialize the SMU for use
RyzenAdj info (using /dev/mem fallback):
no compatible ryzen_smu kernel module found, fallback to /dev/mem
CPU Family: Strix Halo
SMU BIOS Interface Version: 25
Version: v0.17.0
PM Table Version: 64020c
... (STAPM/PPT/THM values follow)
Module appears in lsmod but sysfs path is missing:
$ lsmod | grep '^ryzen_smu'
ryzen_smu 49152 0
$ ls -lah /sys/kernel/ryzen_smu_drv
ls: cannot access '/sys/kernel/ryzen_smu_drv': No such file or directory
Steps to reproduce
Install ryzen_smu (DKMS) on Arch Linux.
sudo modprobe ryzen_smu
Observe dmesg errors above and absence of /sys/kernel/ryzen_smu_drv.
Run sudo ryzenadj -i → falls back to /dev/mem, reports “Strix Halo”.
What I expected
ryzen_smu to recognize this Zen 5/Strix Halo CPUID, initialize successfully, and expose the sysfs interface so RyzenAdj can use it instead of /dev/mem.
Additional context
Under Windows, Universal x86 Tuning Utility (UXTU) can adjust Curve Optimizer on this machine, so SMU accepts CO changes on this platform.
I can provide more details if helpful (e.g., full dmesg, lscpu, modinfo ryzen_smu, SMU/PM table dumps from RyzenAdj).
Request
Could you add support for CPUID 0x00B70F00 (family 0x1A, model 0x70), identified by RyzenAdj as “Strix Halo”? If there’s a WIP branch or a patch to test (e.g., CPUID mapping/platform definition), I can test and report back quickly.