jothi-prasath / auto-epp Goto Github PK

× auto-epp.service - auto-epp - Automatic amd-pstate epp
     Loaded: loaded (/etc/systemd/system/auto-epp.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Fri 2023-09-29 21:49:45 CEST; 5s ago
   Duration: 1ms
    Process: 4456 ExecStart=/usr/bin/auto-epp (code=exited, status=203/EXEC)
   Main PID: 4456 (code=exited, status=203/EXEC)
        CPU: 1ms

Sep 29 21:49:45 fedora systemd[1]: auto-epp.service: Scheduled restart job, restart counter is at 5.
Sep 29 21:49:45 fedora systemd[1]: Stopped auto-epp.service - auto-epp - Automatic amd-pstate epp.
Sep 29 21:49:45 fedora systemd[1]: auto-epp.service: Start request repeated too quickly.
Sep 29 21:49:45 fedora systemd[1]: auto-epp.service: Failed with result 'exit-code'.
Sep 29 21:49:45 fedora systemd[1]: Failed to start auto-epp.service - auto-epp - Automatic amd-pstate epp.

Surface Laptop 15 AMD with surface kernel 6.4 Fedora 38 :(

Hi sir, how can i delete/remove the package from Ubuntu?

Hi,

I have this working in tandem with auto-cpufreq and, after having enabled the auto_epp service and rebooting, the system doesnt seem to acknowledge my .conf file (eg. I wrote BAT=power, but it remains at BAT=balanced_power) even though it shows the service running.

Does this have to do with changing it to active/passive/guided mode?

forgive my ignorance if this is an obvious answer.

Cheers!

So on my laptop there is a "conservative" which basically limits the charge to 80% and auto-epp reports it as on Battery because of this:

sbattery(percent=79.52387907112605, secsleft=<BatteryTime.POWER_TIME_UNKNOWN: -1>, power_plugged=None)

power_plugged is None, when on battery power_plugged=False and when charging power_plugged=True

I fixed it on my end by updating the condition

    if battery.power_plugged is None or battery.power_plugged:

but i'm not sure if that would apply to all the laptops that have similar modes hence i didn't make PR for now.

It does almost the same.

I'm currently submitting this package for nixos ( see PR ) and one comment was raised that it would be better to run the service as DynamicUser and give it the permissions it needs through CapabilityBoundingSet which would make it more secure.

I believe that for this to work, it would need the main script to test write permission on the targeted files instead of checking if the user is root.

Would love it :) thanks