Re: Setting persistant cpupower settings? (Was) cpupower-gui failing to apply config at boot.

On 04-20-2024 06:13PM, Patrick Shanahan wrote:

* -pj via openSUSE Users [04-20-24 19:05]:

...

On 04-20-2024 04:45PM, Patrick Shanahan wrote:

...

* -pj via openSUSE Users [04-20-24 17:35]:

...

Hi, openSUSE Tumbleweed 20240418 is installed on this machine. I am noticing these messages now relating to cpupower-gui in a journalctl -b log output.

https://paste.opensuse.org/pastes/3fa21ae9b076

cpupower-gui has become unable to launch through application menu as well as Konsole now.

I reported a bug on cpupower-gui github page yesterday.

https://github.com/vagnum08/cpupower-gui/issues/119

Started an ICEWM session (I thought it may be KDE related issue). Attempted start from Konsole by passing: # cpupower-gui -p resulting in a failure and output the same as shown in the log file.

Could this possibly be an issue with the newer kernel version? uname -a

6.8.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Apr 15 06:36:47 UTC 2024 (605b284) x86_64 x86_64 x86_64 GNU/Linux

What are your thoughts on this situation?

the app is from a private individual's build, not a regular opensuse supported repro and probably has not been updated to comply with updated packages.

I closed my latest message on github about the problem.

...

...

fwiw, I tried it and it failed to function. but there are several private builds and I am too lazy to try them all. the commandline package is good enough for me.

I think I discovered the issue.

cpupower-gui-helper.service enabled disabled cpupower-gui.service enabled disabled "cpupower-gui-helper.service" was not enabled or started. I enabled the service. I then powercycled the machine. Now: sudo systemctl status cpupower-gui.service

○ cpupower-gui.service - Apply cpupower-gui config at boot Loaded: loaded (/usr/lib/systemd/system/cpupower-gui.service; enabled; preset: disabled) Active: inactive (dead) since Sun 2024-04-21 10:46:03 CDT; 23min ago Docs: https://github.com/vagnum08/cpupower-gui man:cpupower-gui(1) Process: 1109 ExecStart=/usr/bin/cpupower-gui config (code=exited, status=0/SUCCESS) Main PID: 1109 (code=exited, status=0/SUCCESS) CPU: 227ms

Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Minimum Frequency: 2000.0 MHz, Maximum Frequency: 2667.0 MHz Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Governor: Schedutil, Online: True Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Setting CPU: 2 Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Minimum Frequency: 2000.0 MHz, Maximum Frequency: 2667.0 MHz Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Governor: Schedutil, Online: True Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Setting CPU: 3 Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Minimum Frequency: 2000.0 MHz, Maximum Frequency: 2667.0 MHz Apr 21 10:46:03 Thinkcentre-M57p cpupower-gui[1109]: Governor: Schedutil, Online: True Apr 21 10:46:03 Thinkcentre-M57p systemd[1]: cpupower-gui.service: Deactivated successfully. Apr 21 10:46:03 Thinkcentre-M57p systemd[1]: Finished Apply cpupower-gui config at boot. paul@paul-Thinkcentre-M57p:~> cpupower frequency-info analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 10.0 us hardware limits: 2.00 GHz - 2.67 GHz available frequency steps: 2.67 GHz, 2.00 GHz available cpufreq governors: ondemand performance schedutil current policy: frequency should be within 2.00 GHz and 2.67 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.99 GHz (asserted by call to kernel) boost state support: Supported: no Active: no

...

Ok thank you for this information. I am reading this -> https://doc.opensuse.org/documentation/leap/archive/42.3/tuning/html/book.sl...

I haven't read but be aware the doc you quote is for 42.3, not tw.

...

I can use '# cpupower frequency-set --governor ondemand' to set the governor settings.

I have created a systemd.service and service script now in order to have the machine boot with kernel using the ondemand governor and it is working.