Framework Laptop 13 Ryzen 7040 BIOS 3.08 Release BETA - Held

[Will_Nilges]

Do you have the battery extender enabled? Make sure that is turned off.

[Michael_Myers]

After you disable the extender, it may not hold your limit. After going back to Windows it charged past my limit. I went back to the BIOS and changed my limit by 1 percent, now it’s holding.

[Charlie_6]

Framework should test each combination of interactions between charge limit and battery extender, then provide official documentation of setting it in BIOS

[ehsanj]

I have charge limit set to 80% and battery extender disabled. Unfortunately, my laptop is charging all the way to 100%. Since my battery was already charged 90%+ at the time I made the change, I wonder if letting the battery drain below 80% and then plugging in the charger would make a difference. I’ll test that and report back in the AM.

[ehsanj]

So, I let the battery drain to 78% and then plugged in the charger. The battery is at 84% right now, and still charging, beyond the 80% limit (with battery extender disabled).

Assuming the way I have the combo configured is supported, the BIOS update is broken (at least for me). FWIW, I’ve always had the battery charge limit set to 80%.

$ sudo dmidecode --type=bios
Place your finger on the fingerprint reader
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
        Vendor: INSYDE Corp.
        Version: 03.08
        Release Date: 03/19/2025
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 32 MB
... elided ...

$ distro
Name: Fedora Linux 41 (Workstation Edition)
Version: 41
Codename:

$ uname -r
6.13.9-200.fc41.x86_64

[JanW]

After a couple of warm and cold reboots I am happy to report that so far the charge limit works for me, with the battery extender enabled. The charge limit didn’t work initially. It took a cycle of changing the value in BIOS, save and exit, on the reboot change the value back to the previous one, save and exit, until it stuck.

EDIT: The charge limit ended up not being respected with battery extender “on” after a discharge - suspend - resume + charge cycle.

[Adam_Bishop]

I updated to 3.08 yesterday, and, for me, the battery limit (60%) is respected until the computer goes to sleep/suspend (using Ubuntu 24.10). During sleep it just sails past the set battery limit, and when I come back from my coffee break it’s almost charged to 100%. So, 3.05 worked fine, 3.07 didn’t respect the battery limit much of the time, and 3.08 doesn’t seem to respect the battery limit at all during sleep. Plus, now the computer has trouble waking from sleep/suspend (I feel for it), sometimes it takes ages to wake, sometimes I have to press the power button twice (instead of just a key), sometimes it simply won’t wake, and sometimes the mouse pointer is super laggy when it does wake (until I restart it). Granted some of the wake problems may be due to Ubuntu updates, but the battery limit is all BIOS I guess. Whatever the sleep state Ubuntu is setting, shouldn’t the battery limit hold? Fingers crossed some fine code wranglers can figure it out!

[Greg_White]

Charge limit seems to work here, but it doesn’t float. It seems to charge immediately.

Worse, now when it swaps to charge / discharge, it notifies the OS, so it’s as if it is being constantly plugged and unplugged, which is fantastically annoying.

I would just lose the battery extender functionality and focus on getting the battery limit to work right. Or maybe just have battery extender set the limit to the correct % and leaving it at that.

And stop toggling the plugged state!

[Rei]

another data point. I updated via usb (EFI shell) as always, the charge limit is respected, rebooted, sleep/suspend, and left it plugged in overnight, it would only charge up to my set limit.

edit: I have battery extender disabled.

Also tested all usb ports are working.

but like @Greg_White said, changing from plugged/unplugged is annoying.

[Charlie_6]

Does charging using 20~30W charger work?

[wjs]

@Quin_Chou I personally wish the Battery Extender would die a permanent death … but I imagine I am in the minority. I just wish it was optional, not forced upon us.

To that end, could we just make the new Battery Charge Limit functionality, including its new modifications, work as intended/designed, throw in the other non-battery updates, and ship that as 3.08 (or 3.09) for now? I am still on 3.05, and I see no reason to touch any of the updates released up to this point. I don’t think the Battery Extender functionality (and its problems) should prevent users from getting other updates, including security-related ones, any longer.

[pgroheIO]

@Greg_White

Worse, now when it swaps to charge / discharge, it notifies the OS, so it’s as if it is being constantly plugged and unplugged, which is fantastically annoying.

Shouldn’t it be able to maintain a “plugged in, not charging” state rather than toggling between plugged / unplugged? When your battery has reached the charge limit and the laptop is now running solely from the power adapter?

See also:

[TRACKING] Battery flipping between charging and discharging / Draws from battery even on AC

With AC connected and battery charge at the set threshold, the battery status as reported by the kernel often flips between charging and discharging, sometimes even within one or two seconds. (This can be seen using the Gnome battery icon or upower -d). AC is always reported as online. This also means I get a constant stream of udev events starting tlp, which then notices that AC is still online and does nothing, but this could probably be solved by tweaking udev rules. Some more observations: …

[JibberX]

Agreed, Fedora and GNOME are gleefully giving me “you’ve just plugged in” noises to the point I am thinking of turning them off (as they are buried in a mysterious GNOME setting not obvious in the GUI).

[Obasav]

That also can cause performance sacrifices too, as the OS would think it needs to limit wattage to whatever it deems safe for the battery…

[Greg_White]

It definitely does cause performance issues, if you have your laptop setup to throttle on battery.

Worse, if you have the screen brightness go down when unplugged, you get you screen brightness toggling.

As noted, it’s terrible.

Is it possible to revert this BIOS?

[Mathias]

Yes, I use a 30W charger and it works. There are dedicated threads for charger compatibility.

[Greg_White]

Yes, it used to (as of 3.07), maintain the state as plugged but discharging. No problems. As of 3.08, it changes the state to unplugged (running on battery) so that the OS throttles the CPU, dims the screen, makes the unplugged noise and so on.

It should do what it used to do. Maintain the state as plugged but show discharging.

As of now, I have configured my machine to not throttle or dim the the screen when unplugged, and I disabled the plugged notification.

That means that when I go on battery, I need to do all this stuff manually.

I would not install this BIOS until this is resolved.

[pgroheIO]

@Greg_White

Yes, it used to (as of 3.07), maintain the state as plugged but discharging

Why should the battery be discharging if the laptop is plugged-in?

In the scenario where laptop is plugged-in & battery charge limit has been reached shouldn’t the laptop then be powered solely by the power adapter, drawing no power from the battery? Battery-bypass, passthrough, etc…

[Charlie_6]

@Obasav

That also can cause performance sacrifices too, as the OS would think it needs to limit wattage to whatever it deems safe for the battery…

If that’s the case, when I play video games at performance mode I would get spammed by the OS plugged in message and I would get tons of studdering

I guess I’ll stay at 3.05 as I always set charge limit manually

[Greg_White]

Yes you would get spammed by notifications. And your performance would stutter.