tpacpi-bat VS firmware-lenovo

Does someone tested https://github.com/teleshoes/tpacpi-bat on Linux os ?

I use tpacpi-bat in a bash alias that runs something like

Some time ago I installed Ubuntu on my T460 and looked for a utility like Lenovo Vantage for Windows. One of the useful things in Vantage is setting up threshold for battery charging, because this can help to extend battery life. For Linux I found a small and simple CLI utility that can set it. I share it with pleasure: https://github.com/teleshoes/tpacpi-bat

Modify https://github.com/teleshoes/tpacpi-bat so it works with FreeBSD. This script makes use of /sys/class/power which is a path exposed by ACPI on Linux but not on FreeBSD. It defines my $psDeviceGlob = "/sys/class/power_supply/{BAT0,BAT1,AC,ADP0,ADP1}/device/path"; which to me means I can't use this until I've figured out an equivalent path on FreeBSD. I may also have to change the ASL base (for e.g. Thinkpad S2 this is defined as \_SB.PCI0.LPCB.EC.HKEY on line 395). Issue 59 (https://github.com/teleshoes/tpacpi-bat/issues/59) gives a hint on how to port it in a way that I don't fully understand: "you might need to modify the ASL base detection though. no promises."

Windows Update ran this morning and updated a few Lenovo system updates, after which my laptop can now no longer charge. Windows reports it as 0% while the Bios reports it as 7% - has anyone else updated and ran into this? On the below GitHub page, looks to be a known issue but wondered if anyone else has managed a workaround? https://github.com/fwupd/firmware-lenovo/issues/329

Another relevant issue report on github.

ya that service has been very helpful and tracking issues is great, but there can still be issues when installing. For example, I am dealing with a bug found in this list of issues: https://github.com/fwupd/firmware-lenovo/issues on one of my laptops.

Has anyone had any success getting the ThinkPad Thunderbolt 4 Docking Station to work reliably on Linux? I'm running Pop-OS! and as per https://github.com/fwupd/firmware-lenovo/issues/191 it hard crashes (locks) the machine on boot and Lenovo have seemingly abandoned the issue for Linux users, despite the cost of this thing.

Unfortunately a UEFI capsule firmware update actually uses the old version of the firmware to apply the new version. So if you've got a super-old existing version you might need to use Windows (sad face) or a bootable CD to update to a slightly newer version, and from there fwupd can work. Lenovo are supposed to include a "old bios must be newer than X" in the firmware metadata, and so if you can file a bug in https://github.com/fwupd/firmware-lenovo/issues with your old BIOS version included, I can make sure it doesn't happen to anyone else. Sorry!

I have the same issue, as do others (see https://github.com/fwupd/firmware-lenovo/issues/191). Seems Lenovo just don't bother with Linux these days, given it's been 8 months since this was reported.

It does seem that updating firmware might be the only thing to worry about. Do you use the program called fwupd, a.k.a. fwupdmgr? That program works well when it actually works. I have had many problems with it. (See here for problems it has on ThinkPads.) I suggest that you try it (if you have not already) and see whether it works for you. Or, if Pop_OS has some sort of GUI front-end for fwupd (does it?) then try that.

The issue tracker for Linux firmware update troubles with Lenovo hardware is here, BTW: https://github.com/fwupd/firmware-lenovo/issues