As soon as you have a support contract with whom you expect it from.
1 Like
Thank you for the reply. I am afraid that ‘contract with whom you expect it from’ makes little sense. Do you mean that I am expecting a paid level of service for a product for which I have not paid? If so: yet, I have paid. For, I bought a Framework laptop and that laptop is supposed to work with Linux.
You quoted @DHowett before.
He is not involved with Framework.
Neither is the person doing the mainline work for these drivers (me).
It’s a community forum, your messages are read by the community.
You could also have read this very thread which does contain the answers you are “expecting”.
4 Likes
Hi, it’s a while since my last visit to this thread. I tried to catch-up on the status quo today, and my understanding as per last comments is that we need module cros_charge_control to be loaded and its param probe_with_fwk_charge_control to be set.
So I did just that, but KDE still isn’t showing any battery charge limit option. What am I doing wrong?
❯ uname -r
6.11.2-1-default
❯ sudo modinfo cros_charge_control
[sudo] password for root:
filename: /usr/lib/modules/6.11.2-1-default/kernel/drivers/power/supply/cros_charge-control.ko.zst
license: GPL
author: Thomas Weißschuh <linux@weissschuh.net>
description: ChromeOS EC charge control
suserelease: openSUSE Tumbleweed
srcversion: 92B77CD0EA61B7EE89557CE
alias: platform:cros-charge-control
depends: battery
retpoline: Y
intree: Y
name: cros_charge_control
vermagic: 6.11.2-1-default SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: openSUSE Secure Boot CA
sig_key: FA:BE:D8:BF:40:9A:5E:65
sig_hashalgo: sha256
signature: 28:15:FB:17:5E:D3:1F:DF:BE:1C:F6:FE:2C:F6:B6:89:2D:FA:8E:26:
0F:8D:EE:89:56:54:D6:EC:ED:5A:83:56:A5:10:32:A0:4F:7C:C0:FD:
66:C0:56:FB:6B:91:32:27:ED:30:6B:50:D9:6E:2E:18:EC:6B:D7:36:
BF:2B:98:D6:AF:44:1F:9F:DC:22:99:D1:46:11:51:E4:A8:7C:34:03:
88:DB:32:27:8C:A8:00:AD:1B:E7:5B:62:76:42:FA:9D:EA:8C:60:74:
BD:08:3B:F0:59:F8:C8:CD:AA:A2:C0:7C:2E:0E:EF:C3:10:F1:7B:65:
37:B8:0A:B8:26:DE:47:03:D7:38:B9:E5:38:F5:9C:4C:0B:6D:E4:A7:
2C:E6:65:12:B5:5A:CD:2A:51:E3:91:FC:0D:75:E8:85:A2:5F:C7:B2:
76:54:C6:51:36:EB:A3:2A:57:8B:AB:8C:2C:B5:32:4B:C0:AA:20:FA:
A0:05:4C:51:0E:16:2F:CF:CB:90:8C:65:45:AE:06:D6:F4:61:A7:AA:
32:9B:D4:87:70:42:A7:37:C3:BC:96:38:9F:62:A7:2F:4C:4B:C0:CD:
C1:FA:F7:96:41:A8:50:38:95:C9:AE:EA:D5:6F:63:C9:39:90:5E:D5:
CB:29:BA:9E:49:E1:03:17:21:85:C1:2B:50:C5:8D:EE
parm: probe_with_fwk_charge_control:Probe the driver in the presence of the custom Framework EC charge control (bool)
❯ cat /sys/module/cros_charge_control/parameters/*
───────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ File: /sys/module/cros_charge_control/parameters/probe_with_fwk_charge_control
───────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
1 │ Y
───────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Finally, I have also disabled charge control from UEFI, or at least I think so: since I couldn’t find an on/off toggle, I just changed the current value (80) to 100. I guess this would be equivalent to disabling firmware-level charge control (but please correct me if I’m wrong).
Thank you in advance for any help.
P.S. is it because of a limitation that this module can’t control directly the value set by UEFI?
I’ve got the same problem. See Request: Testing of Linux drivers on all laptop models - #22 by Roy_Meissner
Which device are you using? I see your username but want to make sure.
There are two completely separate battery control mechanisms in the EC.
The UEFI is using one, the driver the other.
Also I have no idea how KDE works in this regard.
Donyou have the raw sysfs attributes?
I think I was looking in the wrong place.
Now I can see the setting in the KDE UI (it’s under Advanced Power Settings).
The problem is that now power-profiles-daemon seems a bit messed up, or at least plasma can’t interact with it anymore.
It also looks like once 80% is reached, the battery is allowed to discharge (I’m now at 79%) and I dunno at which point it will fill up again. I’d rather avoid a situation where it constantly goes 80 → 75 → 80 → etc. That’s something that wasn’t happening when using the UEFI charge limit (unless the load on the system was so high, the power adapter couldn’t feed it enough juice to run on electrical outlet power only).
I think I’m back to UEFI charge control, at least for now (EDIT: it dropped to 78% now)
