I'm wondering if there is any way to set custom charge limit for laptop batteries? I've checked out the Power Management docs however it doesn't seem to mention this. Would it be possible to achieve this with APM or similar utility? For me, If this is possible it may justify the purchase of a genuine Lenovo battery replacement.

pfr have you looked at upower ? I haven't but, maybe worthy...

pin The man page is lacking in any useful information. Cant find a whole lot on upower unfortunately. Was hoping there might be a port of TLP in pkgsrc as that works great on linux. I'll do some more searcing, will post back here If I find anything.

you can't control battery charging from userspace. it's the responsibility of the firmware to do the reasonable thing

nia I suppose that's one more reason to coreboot

I don't think coreboot replaces the battery firmware

nia you can't control battery charging from userspace. it's the responsibility of the firmware to do the reasonable thing That's exactly what I would've said, before I looked onto that TLP thing mentioned above. It does look to me now, that some form of battery override is possible, at least on ThinkPad laptops, for setting things like battery charge thresholds. On the ThinkPad wiki: https://www.thinkwiki.org/wiki/Tpacpi-bat https://www.thinkwiki.org/wiki/Tp_smapi There's even code on GitHub: https://github.com/teleshoes/tpacpi-bat https://github.com/morgwai/tpbat-utils-acpi

rvp some form of battery override is possible, at least on ThinkPad laptops Precisely why I want to try it on my supported x230. When I get time I will take a look at tpacpi-bat and see if I can get it working.

pfr tpacpi-bat is Linux-only. (Those scripts just manipulate the kernel-provided /sys/... files.)

Setting battery charge limit

rvp

pin I would, if there was a release tag.

File an issue, then.

rvp I'm nearly sure the lack of releases/tags has something to do with licensing. Its a bit unclear to me if its allowed or not.

rvp

pin I'm nearly sure the lack of releases/tags has something to do with licensing

I never thought of that...However, since Linux -> FreeBSD is OK, I don't think FreeBSD -> NetBSD will raise eyebrows. What's good for the goose is good for the gander.

pfr

pin
rvp

Whats the worst that can happen? If a licensing agreement is breached etc. Can it not just be resolved by a simple apology and removing the package, IF anybody complains? You said it yourself @pin, it's unclear if it's allowed. I'd take that as, it's allowed unless explicitly specified otherwise.

rvp

pfr Whats the worst that can happen? If a licensing agreement is breached etc.

The worst? Well, they could claim your first born you know...

pfr I have no interest in this, redshift does all I need. If someone forks the project and provides a release tag or, the project itself provides a release tag, I might change my mind.

Sorry if that sounds rough but, I won't get involved in licensing mess or in packaging stuff straight from git. If developers want their software packaged, the least they can do is provide a release tag.

rvp

pfr Get over your patchophobia, mate. If you can hack .rc files, then you can surely handle a 2-line patch. Make me and @pin proud.😁

rvp

pin If someone forks the project and provides a release tag or, the project itself provides a release tag, I might change my mind.

There's a thought. Maybe @pfr can get his feet wet by forking and maintaining the patched version on GitHub. I believe he already has an account there.
PS. I've reverted the patch (slightly--to how it was the first time I posted it) to remove -ldrm_intel. No calls were being made into it, and no point in linking it in just to make the patch simple for a fledgling patcher.

pfr In fact, if you could kindly guide me through the steps of how to apply this patch I'll gladly give it a crack.

Start a new thread; then we can all pitch in with instructions.

pfr

rvp
🤣 well, not a phobia per sē, you have just assumed that I know how to apply a patch. I know it may seem like a straightforward task, but I've never ever needed to patch something, so I never learned. And when I google "how to apply a patch" I get nothing but AskUbuntu articles, and every link has a different method and mostly on Linux. So then:

Q. Is a patch file saved as a .diff or a .patch? (I assume .patch but I've seen .diff used as well)

In fact, if you could kindly guide me through the steps of how to apply this patch I'll gladly give it a crack.

EDIT: I guess I'd also like to understand how you create a patch file. I assume it is just a neater solution than manually editing a MAKEFILE?

pfr Here's a patched tarball for you https://ufile.io/tbehm6e0
Follow @rvp's instructions above.

nia

It's clearly under the MIT License though? I think it's more likely they've just been too lazy to tag a release.

pfr

rvp

rvp Maybe @Ramiferous can get his feet wet by forking and maintaining the patched version on GitHub

I like the sound of that. I want to learn how to do this so I'll certainly try.

Gotta get my system working properly first.

nia

intel_backlight is now available as sysutils/intel-backlight. Was pleasantly surprised by it :p

rvp

nia intel_backlight is now available as sysutils/intel-backlight.

"Excelsior!"

« Previous Page