Thomas Weißschuh
Thomas Weißschuh
@bgermann Please try again
In it's current form not at all. Instead we could use `-ffat-lto-objects`. LTO with GCC won't work, but with clang it can.
Maybe you can try to run the CRIU tests on a kernel including commit 69896119dc9d ("MIPS: vdso: Switch to generic storage implementation")
Could you explain how this event gets interpreted by Gnome? The kernel doesn't seem to know to handle it.
In any case you'll need to set `cros_charge-control.probe_with_fwk_charge_control`. What is the output of `ectool inventory`? **You probably need [a patch](https://lore.kernel.org/lkml/20250609-cros-ec-mfd-chctl-probe-v2-1-33b236a7b7bc@weissschuh.net/) to fix compatibility with bios 3.09.**
> You once wrote that this is only needed if framework_laptop is also loaded. It is always necessary on a Framework machine. It is a promise by the user not...
``` [ 13.491349] cros-charge-control cros-charge-control.6.auto: Framework charge control detected, preventing load ``` Seems like your parameter is not set correctly. But it does look fine to me. Did you unload...
> Is it safe to think this will target a kernel 6.17 merge ? If nothing unexpected happens it will make it into 6.17
The currently newest firmware versions will require Linux 6.17. Older firmwares do work with older kernels. The documented module parameter is always necessary, until Framework remove the incompatibility.
@linrunner > Does this apply only to the Framework 13 or to all Framework models? Should be all of them. The specific version number differs by model. More abstractly, firmware...