Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rebuilt battery scripts #645

Merged
merged 2 commits into from
Feb 13, 2024
Merged

Conversation

PurpleWazard
Copy link
Contributor

for some reason python is having a hard time writing to a system file with root permissions so i had to change how the battery scripts write to system files.

also updated the .conf example.

@AdnanHodzic
Copy link
Owner

Code LGTM, but when I started testing it, I ran into few issues, i.e:

when there's no config file present, auto-cpufreq --live returns following:

sudo auto-cpufreq --live

Note: You can quit live mode by pressing "ctrl+c"

----------------------------------- Warning -----------------------------------

Detected running GNOME Power Profiles daemon service!
This daemon might interfere with auto-cpufreq and has been disabled.

This daemon is not automatically disabled in "monitor" mode and
will be enabled after auto-cpufreq is removed.


-------------------------------------------------------------------------------

Linux distro: Ubuntu 23.10 Mantic Minotaur
Linux kernel: 6.5.0-17-generic
Processor: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Cores: 8
Architecture: x86_64
Driver: intel_pstate

------------------------------ Current CPU stats ------------------------------

CPU max frequency: 4600 MHz
CPU min frequency: 400 MHz

Core	Usage	Temperature	Frequency
CPU0      0.0%        46 °C      4559 MHz
CPU1      0.0%        42 °C      4474 MHz
CPU2      1.0%        43 °C       400 MHz
CPU3      0.0%        45 °C      4450 MHz
CPU4      0.0%        46 °C      4531 MHz
CPU5      0.0%        42 °C       400 MHz
CPU6      3.0%        43 °C      4430 MHz
CPU7      0.0%        45 °C       400 MHz

CPU fan speed: 0 RPM

---------------------------- CPU frequency scaling ----------------------------

Battery is: charging

Setting to use: "performance" governor
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
/usr/local/bin/cpufreqctl.auto-cpufreq: line 105: echo: write error: Device or resource busy
Setting to use: "balance_performance" EPP

Total CPU usage: 0.9 %
Total system load: 0.49
Average temp. of all cores: 44.00 °C 

Load optimal (load average: 0.49, 0.62, 1.00)
setting turbo boost: off

-------------------------------------------------------------------------------

		"auto-cpufreq" is about to refresh ..

but it works fine with config file present.

@PurpleWazard
Copy link
Contributor Author

I not getting any errors with --live even without a conf file
Also note --live doesn't have the battery function in it only --monitor and --daemon

@AdnanHodzic
Copy link
Owner

AdnanHodzic commented Feb 13, 2024

Also note --live doesn't have the battery function in it only --monitor and --daemon

Let's make sure this is mentioned as part of #644 as there could be many questions about this.

Other then, that thank you for your contribution! Will make sure this one is also mentioned as part of 2.2.0 release.

@AdnanHodzic AdnanHodzic merged commit 539914a into AdnanHodzic:master Feb 13, 2024
rootCircle pushed a commit to rootCircle/auto-cpufreq that referenced this pull request Feb 16, 2024
* rebuilt thinkpad and ideapad

* updated conf example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants