The submitted patches have the problem that they change the way that the sysctl communicates with the kernel driver. This means that this not only affects Pocket Reform but also classic Reform. It further means that if this would get merged, then all users of all MNT hardware would be required to upgrade their sysctl (pocket reform) or lpc (classic reform) firmware to the new version or otherwise the lpc driver looses the ability to communicate with the system controller which in turn means not only no battery information but also no power off or reboot. For the lpc (classic reform) an update to the firmware supporting this doesn’t even exist yet. And even if it would exist, updating the lpc firmware of classic reform is a bit more involved than updating the sysctl firmware of the pocket reform because you require a second computer with the right software installed and have to open up your device. Thus, we would like to find a solution which does not force every MNT user (pocket or no) to upgrade their firmware or otherwise they cannot really continue using their devices. This topic also got mentioned in IRC last week: 2025-05-14.log
Thanks but I am going to play it safe and wait for the final patch.
I’m looking a bit more deeply into the root causes of this now.
Meanwhile.. I ran apt updat/upgrade to day and on linux 6.14.6-1~exp1+reform20250528T152822Z the dmesg voltage jump messages seem to have gone away but the rest of the problems remain: battery status jumps to 0% and back to whatever it was and system spontaneous hanging / rebooting when not connected to pd usb.
minute is working on fixing this problem for good here:
- pocket sysctl fix: Sysctl SPI rework (!42) · Merge requests · Reform / MNT Pocket Reform · GitLab
- classic reform lpc fix: Classic Reform LPC SPI rework (!84) · Merge requests · Reform / reform · GitLab
- reform-tools dkms kernel module fix: LPC driver: bump speed by 10x; simplify error handling; add uart command support (!127) · Merge requests · Reform / MNT Reform Tools · GitLab
Updated (keyboard and system firmware, and apt full-upgrade) a couple of days ago and have not experienced any power drops or reboots on battery power (though I mostly run connected).
Thank you! 
Unfortunately the problem still exists. 
The machine just rebooted spontaneously running on battery power.
Running connected to power, I got the following different in the kernel messages (from dmesg):
[ 2235.394683] power_supply BAT0: driver failed to report `voltage_now' property: -16
[ 2235.446680] power_supply BAT0: driver failed to report `voltage_now' property: -16
[ 2263.082335] power_supply_format_property: 1 callbacks suppressed
[ 2263.082342] power_supply BAT0: driver failed to report `voltage_now' property: -16
[ 2263.126335] power_supply BAT0: driver failed to report `voltage_now' property: -16
[ 2263.174345] power_supply BAT0: driver failed to report `voltage_now' property: -16
[ 2263.218488] power_supply BAT0: driver failed to report `voltage_now' property: -16
[ 2263.254338] power_supply BAT0: driver failed to report `voltage_now' property: -16
[ 2263.294619] power_supply BAT0: driver failed to report `voltage_now' property: -16
Connected to power, I’ve not experienced a spontaneous reboot.
Not sure if this is related but the problem occurs now when running some large compile job (load avg 8).
I am at:
- linux: 6.15.4-mnt-reform-arm64
- sysfw: PREF1SYSR120250623
- hid: PREF1HID20250623