Hello! I have made changes to my battery driver, so that it will be loaded properly into the system when the battery is detected at startup.
The current version basically just takes over the I2C bus. Not really playing nice in the environment.
Anyway, its available on github under the branch “overylay_driver_possible”. if you know how to use git, and want to pull it down and help me test, I’d appreciate it.
Thanks!
https://github.com/JeffCurless/argon-oneup
Jeff
Hi Jeff, the latest update isn’t working for me. The battery status is stuck at 100% and ‘plugged in’, even when it’s not. Rolling back to the main version fixed the issue.
Thanks… I did forget to mention that you need to remove the old driver first… very odd as I’m watching the battery percentage drop here…
What OS were you running
And … Can I get a copy:
dmesg -T | grep oneUpPower
If you try it again…
Hi,
I believe the issue arose because the previous DKMS module wasn’t uninstalled before the new version was installed. It’s working fine now.
I’m running RPI OS Lite, with Gnome Descktop.
pablo@ArgonONEUp:~ $ dmesg -T | grep oneUpPower
[dom mar 1 09:00:43 2026] oneUpPower: loading out-of-tree module taints kernel.
[dom mar 1 09:00:43 2026] oneUpPower: Changing automatic shutdown when battery is below 5%
[dom mar 1 09:00:43 2026] oneUpPower: Checking battery profile…
[dom mar 1 09:00:43 2026] oneUpPower: Battery profile is valid.
[dom mar 1 09:00:43 2026] oneUpPower: Probe successful (v1.0.3)
[dom mar 1 09:00:43 2026] oneUpPower: AC Power is disconnected.
[dom mar 1 09:00:43 2026] oneUpPower: Battery State of charge is 74%
[dom mar 1 09:04:51 2026] oneUpPower: Battery State of charge is 73%
[dom mar 1 09:11:11 2026] oneUpPower: Battery State of charge is 72%
[dom mar 1 09:19:51 2026] oneUpPower: Battery State of charge is 71%
[dom mar 1 09:28:47 2026] oneUpPower: Battery State of charge is 70%
[dom mar 1 09:37:31 2026] oneUpPower: Battery State of charge is 69%
[dom mar 1 09:46:09 2026] oneUpPower: Battery State of charge is 68%
[dom mar 1 09:55:03 2026] oneUpPower: Battery State of charge is 67%
[dom mar 1 10:04:45 2026] oneUpPower: Battery State of charge is 66%
[dom mar 1 10:14:25 2026] oneUpPower: Battery State of charge is 65%
[dom mar 1 10:23:27 2026] oneUpPower: Battery State of charge is 64%
[dom mar 1 10:32:00 2026] oneUpPower: Battery State of charge is 63%
[dom mar 1 10:39:41 2026] oneUpPower: Battery State of charge is 62%
[dom mar 1 10:46:44 2026] oneUpPower: Battery State of charge is 61%
[dom mar 1 10:53:39 2026] oneUpPower: Battery State of charge is 60%
[dom mar 1 11:00:38 2026] oneUpPower: Battery State of charge is 59%
[dom mar 1 11:08:06 2026] oneUpPower: Battery State of charge is 58%
[dom mar 1 11:16:10 2026] oneUpPower: Battery State of charge is 57%
[dom mar 1 11:24:42 2026] oneUpPower: Battery State of charge is 56%
[dom mar 1 11:33:31 2026] oneUpPower: Battery State of charge is 55%
[dom mar 1 11:42:30 2026] oneUpPower: Battery State of charge is 54%
[dom mar 1 11:51:40 2026] oneUpPower: Battery State of charge is 53%
[dom mar 1 11:56:43 2026] oneUpPower: Battery State of charge is 52%
Thanks!
@NHHiker thank for work you do on this . so far it ok , run on Arch based EndeavourOS . testing it on sway community Edition
eos@OneUp~ $ sudo dmesg -w | grep oneUpPower
[ 5.249099] oneUpPower: loading out-of-tree module taints kernel.
[ 5.253962] oneUpPower: Changing automatic shutdown when battery is below 5%
[ 10.783678] oneUpPower: Checking battery profile...
[ 10.862357] oneUpPower: Battery profile is valid.
[ 10.862614] oneUpPower: Probe successful (v1.0.3)
[ 10.874036] oneUpPower: AC Power is disconnected.
[ 10.883569] oneUpPower: Battery State of charge is 82%
[ 333.595798] oneUpPower: Battery State of charge is 81%
[ 345.882886] oneUpPower: AC Power is connected.
[ 349.979161] oneUpPower: Battery State of charge is 82%
[ 375.577794] oneUpPower: AC Power is disconnected.
[ 386.841435] oneUpPower: AC Power is connected.
[ 438.040149] oneUpPower: Battery State of charge is 83%
[ 510.741941] oneUpPower: Battery State of charge is 84%
[ 581.395804] oneUpPower: Battery State of charge is 85%
[ 653.073688] oneUpPower: Battery State of charge is 86%
[ 723.727605] oneUpPower: Battery State of charge is 87%
[ 745.230550] oneUpPower: AC Power is disconnected.
[ 881.423022] oneUpPower: Battery State of charge is 86%
[ 1177.360047] oneUpPower: Battery State of charge is 85%
[ 1333.012066] oneUpPower: AC Power is connected.
[ 1376.021077] oneUpPower: Battery State of charge is 86%
[ 1447.701653] oneUpPower: Battery State of charge is 87%
[ 1519.381780] oneUpPower: Battery State of charge is 88%
[ 1593.109605] oneUpPower: Battery State of charge is 89%
Edit (AC Power disconnected + connected ) that me unplug / plug power back in .
Thanks guys! I’ll add some code to the install to automatically remove the old stuff… prior to moving new files over.
Jeff
This maybe a really stupid question, but to remove the file and dkms for the prior version of the battery driver, do I use the ./remove script provided?
Hi Jeff,
just installed your driver and since it was a first run (before your older versions), I can say it works as intended. I did, however, play with it on having the argon script running/disabled to see if they interfere. So far, works well on both counts. The system is rpi legacy (for now I am not moving on to Trixie since there are some known issues when running Asterisk on it).
Hi Jeff. I have been using the “overylay_driver_possible” branch for a few days now. It looks good so far. No difference for me when running from charger or battery from the “main” branch. Thanks for all your work on the driver. A real game changer from the provided script that puts the battery status on the desktop.