Rick

I made good progress today. I have added a new command line option to `gpu-ls`. The `--force_all` option will attempt to read all relevant sensors regardless of the classification of...

Looks like the code I added to determine system type systemD vs systemV can not run on your system. Seems like os.path.islink throws an error on your system. I will...

I completed some major work. Hopefully it addresses all of the issues that we have seen on your distro. I have tested on 4 of my systems with a wide...

I have rewritten significant sections of code to give me more flexibility to manage GPU lists and better manage capability in the various applications. I have tested on my systems...

I have done a major rewrite of the plotting related code. It should now work with all AMD APU and most AMD Legacy GPUs. Can you give it a try?...

Thanks! Seems like all is well. Seems like the attachments by responding by email do not make it into an issue update. It would be cool to see, so post...

I would like to add you to the credits: *@Marjorie-R - Testing, Debug, Verification of AMD-APU Capability* Let me know of any concerns.

> On Mon, 2022-05-09 at 06:34 -0700, Rick wrote: Looks like the code I added to determine system type systemD vs systemV can not run on your system. Seems like...

I noticed that this error is occurring within a try/except. It should be handled and result in no valid data read from p-states.

There is 2 sources of p-state data: - P-state table in the `pp_od_clk_voltage` file is a complete table but only available when overclocking is enabled. Used by `gpu-ls` but not...