ryzen 7 4800u (renoir) here. cant execute the included script because of the "unsupported" error. Just removing this check does not work. What should i do?
@leogx9r I emailed you a pm table from my 3900x a few weeks ago, along with some more info, as I was unsure if the pm table was something that is smart to send publically, although now it looks like there shouldn't be any problem with that. Not sure if you noticed the email tho, so, pointing it out here just in case
The monitoring tool is only intended for a 3700X/3800X. For other processors you'll need to reverse-engineer the PM table via dumps and adjust the tool's source code so it can display the relevant information correctly.
Did anyone manage to reverse engineer PM table version 0x00370003? I saw that it was already uploaded a few times, but I also made a dump:
model name: AMD Ryzen 3 4300U, code name: Renoir
pm_dumps_00370003.tar.xz
@leogx9r Do you have any tips on how to do the reverse engineering?
after upgrading the BIOS to the newest (ASRock X570 Pro4 BIOS 4.00, AGESA 1.2.0.0), and and also pulling/installing the newest ryzen_smu driver (0.1.2), ryzen_smu says this PM Table (00380905) is not supported yet. I have created the dumps and attached them. Hope this helps. pm_dumps.tar.gz
Linux b0rg 5.11.0-16-generic #17 (closed)~20.04.2 SMP Fri Apr 23 18:06:13 CEST 2021 x86_64 x86_64 x86_64 GNU/Linux
ryzen_monitor is a different project. You'll need to contact their own developer to add support for that PM table version. The driver itself already has support added in commit 71153d9e.
Please check if it's working on your CPU and if you find bugs (there are for sure).
You need ryzen_smu from my fork to use it: https://gitlab.com/mann1x/ryzen_smu
works way better!
here is the new set of dumppm_dumps.tar.gz
if I run ryzen_monitor, I see 2 sets of results : one with core 0 and 2 sleeping, core 1 and 3 working, and a another set with core 1 working, 0 2 and 3 sleeping...
if I run rysen_monitor -d, I see 2 sets too, same first one, second one with core 3 working, all others sleeping
Good, thanks for the info.
It's not detecting the disabled cores.
I'll add the hack I used for Cezanne to create a fake fuse.
Please send me the output of:
I've just git-clone ryzen_monitor. but even if I can see you have uploaded a new version, when I run it, it still pretend to be "Version: v2.0.1 (NextGeneration - ManniX fork)"?
by "masking the sleeping cores", you mean in the output of ryzen_monitor, the raw between "Electrical & Thermal Constraints " and "Core Statistics (Calculated) "? if so, then no, nothing is masked, I still have 4 cores, some sleeping, some working
my mistake, it looks like system information, except, the label "system information" is not display... and no, I see the first set, with sleeping cores (0W, 0V, 0C...)
I have fixed the enabled_cores but it doesn't explain why you would get inf.
The calculation should have been done in any case, just with wrong values.
I've updated to 2.0.4, let me know.
here is what I see:
╭─────────┬────────────┬──────────┬─────────┬──────────┬─────────────┬─────────────┬─────────────╮
│ Core 0 │ Sleeping | 0.075 W | 0.231 V | 44.50 C | C0: 3.7 % | C1: 6.3 % | C6: 90.0 % │
│ Core 1 │ Sleeping | 0.045 W | 0.222 V | 44.21 C | C0: 2.4 % | C1: 4.6 % | C6: 93.0 % │
╰─────────┴────────────┴──────────┴─────────┴──────────┴─────────────┴─────────────┴─────────────╯
╭── Core Statistics (Calculated) ───────────────┬────────────────────────────────────────────────╮
│ Highest Effective Core Frequency │ 92 MHz │
│ Highest Core Temperature │ 44.50 C │
│ Highest Core Voltage │ 0.231 V │
│ Average Core Voltage │ inf V │
│ Average Core CC6 │ inf % │
│ Total Core Power Sum │ 0.120 W │
if I stress cpu, C6 fold to 0 and Average Core CC6 becomes NaN.
as I've suggested, average core voltage and core CC6 are calculated by dividing total_core_voltage and total_core_CC6 by sysinfo->enabled_cores_count (line 212). if sysinfo->enabled_cores_count is 0, then inf is found. and if total_core_CC6 is 0 too, 0/0=NaN.
I'm rewriting the whole fused core detection function. But it takes time, a lot of disassembly to go through.
Now I'm going to a fair for the weekend so I'll ask you to test again next week.
Maybe I've found the reason why the PM table for your CPU is messed up, hopefully it'll be properly populated and you can get the same info like the other CPUs.